I almost do not know Drupal at all, but I have a project which was created with Drupal.
I setup the Drupal locally. And read a few of the tutorials from over here. I read about Menu, Block, Regions, Themes and Layouts, but that did not help me to understand how to run the existing Drupal project.
Here, by the way is the screenshot of the project:
So, I would be grateful if someone explained me how to run a Drupal project or provided me a link to the guide on how to do it.
I am not intended to learn the Drupal in depth or develop something in it. I want just to made minor changed to the existing project.
Thank you.
This question is very broad and I'm almost sure that it be will down voted and closed, but I'll try to help before that happens. :)
So, to run drupal (or any similar php based) project you must have web server with support for PHP running and this code inside some web root directory defined in web server settings file. You'll also need mysql server running. Easiest way (for local experimenting/development) would be running WAMP server or some similar solution:
http://www.wampserver.com/en/
Then, when you set up web server and your site url, when you visit it for the first time Drupal will recognize that project has to be set yet and lead you trough set of forms for setting up the project. At end you will have functional site.
If you face any problem please be more specific what the problem is.
We already have the same question here i.e. URL for installing Drupal
Here is detailed answer of this question i.e. https://stackoverflow.com/a/53645101/2089994
For more technical articles, have a look at http://etutorialz.com
Related
I'm really keen to use the 2sxc environment on my website for a number of applications.
I'm currently looking at the Mobius forms.
What I'm wanting to do is create a ticket in ConnectWise rather than send an email, using the ConnectWise REST API.
Some of these questions might have obvious answers to someone who has been taught in these technologies, but I'm self-taught. When I went to school I learnt COBOL!
There is c# code in the application, but I can't see how you build and incorporate into the application. I forked the code and it seems to just code with no build.
There are live and staging folders with the same cshtml files. However, it seems a bit random when the live or staging is actually used. For example, I did a quick fix to the _Contact Form.cshtml so to fix the type that meant it always displayed the ReCaptcha warning, and I changed the live version, which didn't do anything, so I had to change the staging version.
I need to update the settings so that configure the ConnectWise API settings, I haven't been able to find where I can do this? I am still looking though.
I also need to store a private key in the settings. Is there a secure way I can do this?
PS. When I get my head around all this I'm happy to be a contributor
welcome to StackOverflow.
I'll try to give you some guidance to help you figure it out
Live and staging are folders meant to let you make changes while the users see the unmodified output. So a host-user sees the files from staging, others see what's in live. When you're done and all is tested, you copy from staging to live. This we call Polymorphism.
Polymorphism applies to both the cshtml as well as the api. So as a host-user, you'll be using staging/api/FormController to save/send.
There is no build process, everything is hot-compiled. That's one of the things that makes 2sxc so amazing. No Visual Studio, DLL or restarting the application ;) You'll love it.
Secure keys: there is no special secure key storage. We usually put it in the App-Settings, just like the MailChimp key you'll see there. We split it into two fields for very technical reasons, because we publish our code on github and that causes trouble when our code has API keys. But you can just use one field, assuming you don't plan on publishing the code on github.
I have been creating a SPA from an empty ASP.net Project and i want to integrate Azure AD Authentication to the project.
Anyone know of any good step by step guide to do this or something similar?
I was reading a bit on this post by Microsoft, but I don't think I understood it quite well.
Error During Authentication Detection
My best suggestion here is to simply follow one of the open source solutions for single page applications which you can find on our GitHub here:
https://github.com/Azure-Samples?q=singlepage
Along with the full source code for all the working solutions, we also provide instructions on registering your app, configuring it, and running the sample.
Another thing that is brand new, which you might find helpful is our Application Quick Start which is available here:
https://identity.microsoft.com/Docs/Web
This does not exactly tackle the intricacies of a Single Page Application, but should be a really quick way for you to just copy and paste code which enables your app to use Azure Active Directory Sign-On.
Let me know which one you found better helped you and why! We would love to hear more feedback here on the investments we are making in documentation.
I am developing website by using word press. Now I am developing in live directly.
I recently get to know we can develop in local-host also. But I don't know which method is preferable and how to develop locally. If developing locally is good. Could you please suggest me the process too.
If you are developing your site in localhost. That's ok. But now problem arises here:
Uploading local site to live will be large time. Suppose that your site is about 150MB. Then it will take long time to upload.
Second problem is that all your featured image, media uploaded file or plugin may be reinstall again. Not sure, but may be.
You will have to change each path that you defined in localhost.
But if you are developing your site in live. Then it's very good.
Simply 4MB or 5MB wordpress files will not take long time.
There is no need to change any path
Since I am a wordpress developer so, I will prefer you to work on directly in live env.
Any help regarding this topic will be welcomed.
IMO, this really boils down to the characteristics of your Internet connection. If your connection is slow/unreliable/expensive, it would be better to develop locally first and then migrate to live when the dev work is completed. If the connection is not an issue, you can save yourself the trouble of migration by developing directly on live.
Another case in favor of live dev is if you need to show/share the work in progress with a client/others.
Finally, if/when you need to do local to live (or any other type of) migration, you can use this (excellent) plugin - works like a charm:
https://wordpress.org/plugins/duplicator/
I develop on a local machine a Wordpress site and I'm now looking for a mechanism to deploy it easy and fast. I'm thinking about a DEV environment (located on my local machine), a STAGING environment (a subdomain on the client page, maybe staging.example.com) and of course a LIVE environment (example.com)!
My current workaround:
As I work with Aptana I'm able to sync my changed files with the deploy mechanism the IDE provides. Exporting my local database, finding/replacing the permalinks and importing the whole thing - finish! To deploy live, I have to replace all staging files with the live files.
This should be easier! Is there anyone out there, having a better workflow?
I'm open and really excited about your ideas!
Thanks a lot
greetings
Yep, it's frustrating and completely insane that Wordpress requires this process because they put absolute urls in the database. I develop in a similar fashion using multiple staging sites for qa and client review. After my first deployment with Wordpress I almost gave up on the platform entirely. All of the solutions recommended by core developers and others simply didn't work.
So I wrote a plugin: http://wordpress.org/extend/plugins/root-relative-urls/
that fixes the problem. With this plugin you don't need to do a search & replace on your content. No hosts file hacks, or dns tricks. With my plugin you can access the site via IP address or Computername or any type of forwarded host. And since it converts urls to root relative before they enter the database, you won't have to worry about them working between the different domain formats. And since they don't hard-code the scheme (http/s) in the url you won't have to worry about the 520 or so bugs that were reported in the wordpress trac database if you use SSL.
It's a staple for any wordpress project I work on these days. And I have written a couple other plugins to deal with idiosyncrasies that exist in the platform that you can check out here: http://wordpress.org/extend/plugins/profile/marcuspope
Hope that answers your problem.
I use Capistrano https://github.com/capistrano/capistrano/wiki/ for all my deployment needs and it is really good solution. You can simply script anything and it just works.
It could work for your deployment scheme too.
I also use Capistrano for both WordPress and Drupal deployments. I typically install modules locally for testing then push to test and production environments. For uploads, etc. I add custom tasks to manage syncing files stored in scm and those that are not. Here is a simple guide I put together.
http://www.celerify.com/deploy-wordpress-drupal-using-capistrano
We are a software development company and are using Wordpress for static portion of the web site. Naturally, all our workflow is built around version control: multiple developers -> continious integration -> staging -> deployment.
Our challenge with integrating Wordpress into our workflow is that its database is stuck like a bone in the throat: you cannot put it into the version control, easily roll back, promote from staging to production etc.
I am wondering what people do in similar situations? I would like to find a way to integrate WP into the development workflow and not the other way around :-)
Clarification we want to "develop" and test pages on the staging system and when ready then move them over to the production as part of the version upgrade process. We don't want to do full replication of the staging database to production.
That's a common question and one that I've worked on tackling. I've written some code to address these issues albeit the code's not ready for distribution. Basically the idea is to create scripts to import the content and then version control the scripts. (Actually my approach uses a custom import/export format designed to be easy to hand-modify, but the idea is similar.)
Anyway, there are some related questions over on StackOverflow's sister site WordPress Answers:
Questions tagged with the term [staging]
Questions tagged with the term [deploy]
UPDATE
Per the clarification, this would probably be helpful too:
Is there any way to draft a revision of a published page or post? What workarounds have you used?
Hope this helps.
-Mike
I've just hit the same problem. For now we are using MySQL dump files to export/import database content, but it gets ugly with several people working on the database changes.
Since the team that works on the project is all internal and consists of just a few people, I'm thinking into the direction of locking the database dump file in VCS. Subversion had this functionality built-in, but we are using git, which, I think, is conceptually opposite of any kind of locking.
Probably we'll have a workaround script with pre-commit hook to check for the existence of a lock file next to the dump. The person who committed the lock file will be the only one allowed to commit the dump. Once he finishes the work, he will need to commit the removal of the lock file.
It sounds ugly, I know. But I've thought about it for a while and don't see an elegant solution yet.
If you're only using WordPress for static content, then any tool/methodology for version controlling databases should work - for example, work the mysql command line tools into your CI and deployment routines.