Drupal multisite files directory

We'll also briefly discuss how to best approach setting up multisite environments on production servers including Ubuntu Linux, and using a more common cPanel solution on shared servers. First let's start by configuring a multisite development environment on our local development environment. You have already prepped your multisite environment in the previous chapter when we set up a Drupal site on our localhost using MoWeS Portable applications.

So, we have the base Drupal core site set up. Our core Drupal site is working smoothly, and in the previous chapter recall that we also configured Memcache API and Authcache to run caching mechanisms on our site.

To make things simple, I'm going to just duplicate this site and use the same content for the two new sites. Once we complete the multisite configuration, all three of our Drupal sites will be running from their own database, but they will be sharing the core codebase, core modules, and themes. The first thing we need to do is create folders for each site we want to run.

So, we're going to add two sites and create the following folders in our. So you'll have:. The reason you do this is that each multisite needs to have its own settings. We'll change those settings in a moment. We're going to create two new databases one for each of our new sites. To do this I'm going to use the same data that my core database contains. Then I'll import that data into each new database that I configure. Here are the steps:. Type in a new username in the text field box and set the host to localhost.

Type and confirm a password into the Password field. This will be the username and password for your new site's database, so make a note of this because you will be re-entering this information into your site's settings.

You will need to know the database username, password, and database name. Click on the Check All link in the Global privileges section and then click on Go. This will create the new database. Repeat steps 5 to 9 to create a database for your second multisite site. Now you have both databases created. Applications Drupal settings Wordpress Settings 8. Edit this page. Drupal Multisite Drupal allows separate, independent sites to be served from a single codebase where each site has its own database, configuration, public files folder, and base domain or URL.

Follow these steps to setup multisite on Docksal: Create a Database A default database is created with every project that uses the default stack, but each multisite requires its own database. Feedback Was this page helpful? The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How do I set up multiple sites with one database or multisite Apache configuration?

Ask Question. Asked 7 years, 11 months ago. Active 1 year, 7 months ago. Viewed 3k times. Improve this question. SenthilKumar SenthilKumar 2 2 silver badges 11 11 bronze badges. I think you forgot to restart Apache: sudo service apache2 restart. Troubleshooting Drupal multi site may be painfull. If you have a terminal to the server, you may have try strace , which gives you you a better idea of how Drupal reads your filesystem see more here drupal.

Add a comment. Now that we have done this two times, this is fairly straight forward. This site relied heavily on taxonomy and they had some interesting taxonomy fields happening. One note is that the data manipulation with a Drupal 8 to Drupal 8 migration is non existent.

So there is really no super fancy process magics needed, even for entity reference fields. Here is one the migration yamls that got the job done:. This vocab had a user and a file entity reference on it. Like I mentioned, everything is almost a one to one line up so writing these yaml files was pretty quick and easy.

Now it is on to your final migration, the nodes. The nodes were fairly quick to setup. We were only moving half a dozen types and there weren't anything crazy about them in general. Here is what I used for their Article type:. So with these migrations all setup and working, we were able to have a repeatable process in place for the task at hand. It didn't take all that long and everybody won in the end. When I was writing these migrations I came to realize that the core Drupal 8 source plugin solves an age old issue.

When you have a site that is architected poorly and you need to move data to a new type, you can easily achieve this now. You can use the same methods I did above and have whatever site you are working on in better position.

This is why the migrate module suite is so powerful.