![]() The script will loop through all the folders in the subsite directory (excluding the Default folder) and will run `drush updatedb` on them all. I was about to write a script when I found that someone else had written one that I could use. Updating each site manually would be time consuming, and a site could easily be missed. Since our intranet has a site for each department, we have several dozen subsites to manage. This can cause subsites to have the White Screen of Death their modules have been updated, and their modules expect the database to have been updated as well. If you don't run the updates for each site, then only the main (default) site will get the proper database updates. Subsites share the same Drupal core and module code, but they have their own database and tables. Because module updates can alter the database structure (modules can have their own tables), database updates must be run for each subsite. Recently, I discovered that we were missing a crucial part in the update process. They may not all have the same modules enabled, but they all have the same versions available. Thus, updates are relatively easy, as you only need to do a single core and module update for the changes to be reflected by all sites. With our setup, they also share modules, libraries, and themes. I've written a few modules here and there, but one of the biggest things I've done is set up our Intranet websites using a multi-site setup in Drupal.Ī Drupal multisite is mainly a bunch of sites that, behind the scenes, share the same Drupal core. It has been fun to learn Drupal, teach other people how to manage their own pages, and learn how to administer the site. We have moved our public facing website over to Drupal 7 from a home-grown java based site. Is there a $PARENT type variable like I described that we can use? If not, how hard would it be add into Virtualmin?Ģ.Drupal has become a big part of my job in the last year and a half. The two issues I see with this that maybe Joe can answer:ġ. The new Sub-server can still have email, it's own database, it's own database user, it's own DNS zone records, etc. That should then work perfectly, because now the Sub-Server would point to the Drupal Root directory. What I mean is on the 'Apache Website' page when editing a 'Server Templates', in the text field called 'Directives and settings for new websites' we need a way to set the DocumentRoot and Directory options to $PARENT/public_html or something like that instead of $HOME/public_html. I'll ask Jamie to have a look at this thread and comment on how he thinks something like this ought to work.Īfter sleeping on it I think all that we need to get Drupal multisite working smoothly is a Virtual Server for the main domain and Sub-Servers for the additional domains, but we need a way to reference the parent Virtual Server's home folder in the file system. I'm going to be tinkering with this some, it might be something we want to fiddle with in Virtualmin.allowing databases and more of the other features in Aliases, so they fit this deployment better. ![]() A Drupal installation is tiny (about 8MB).even with a ton of modules it's only a few tens of MB. Upgrades of Drupal core can be easily handled across all of your domains by Virtualmin. That'd be one way to go about it.Īll that said, unless your sites are really identical (except name and content), I'm not sure there's a real benefit to a single install of Drupal. And, you could create your databases manually. ![]() But, from a Virtualmin perspective it is pretty similar.Īnyway, you can do mail boxes (I'm pretty sure) for Aliases. Though I currently do not plan to run separate databases (just different domain landing pages for and and ).so it's a different set of problems. So, I'm going to be digging into this very problem pretty soon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |