#DRUPAL CONSOLE SITE INSTALL MULTISITE UPDATE#
#DRUPAL CONSOLE SITE INSTALL MULTISITE UPGRADE#

The disadvantage being that when one of the sites produces a bug, this will possibly be the case for all your sites.

Easily share content, media and users between the multiple sites.

Updating of fixing bugs in the multisite will automatically transfer to all other sites. If you're tasked with maintaining multiple websites, which are more or less the same when it comes to functionality, than a multisite is the way to go. If you want to know more about the difference between the two options check out this Multi-site vs. So when I'm talking about a multisite, I'm talking about a multisite solution with Domain Access. I prefer the second option because sharing content, users and improvements between the websites is one of the things that makes a multisite solution great. Also, if you create new functionality such as a new paragraph type or a search API view, all sites can profit from these improvements. In this case the database is shared, making it possible to share content and users between the sites. Each domain can be accessed via it's own URL.

Multiple websites with the Domain Access module: With the Domain Access module it is possible to create different domains within your Drupal website.

Because the database is not shared every website has their own content, users and functionality. Think of modules or a specific configuration. Having a multisite solution like this can be useful when you have multiple websites that have different needs.

Traditional multisite functionality: This is where the codebase (files for the core, modules and themes) is shared but each site has their own database.

When you want to create multiple websites from one codebase with Drupal you have two options: Both sites have their own domain name, and if needed their own look and feel. So a visitor can access these sites via different domain names, but in reality they are all served from the same source.Īn example would be a company having a corporate website and a separate website where they post jobs opening within the company. I need a couple of features before I'm able to use c5 for all my projects.īecause of that it's a bit difficult to say what this feature is worth.When I say multisite I'm talking about a website which consist of one single codebase and database, but has the functionality to virtually create multiple websites. Right now there's just a one problem - c5 is not ready for all my customers. Good question - I wanted to implement what I wrote above on my own.Īs soon as I have a few more customers running c5 this feature is pretty much a must have. My servers don't have ftp, only sftp which might be a problem too because as far as I know php only supports 'ftp' and 'ssl ftp' (which is not sftp!) There is part of the web server or part of something like google analytics. This is not a concrete5 that could host more than one page but it would make it much easier to work with a hundred installations. You could then execute a couple of functions from this point like A small php application where you simply enter the ftp credentials to all the sites you want.

#DRUPAL CONSOLE SITE INSTALL MULTISITE UPDATE#

Since it is quite difficult to update a c5 installation using php code it thought it might be nice to have a separated 'c5 update/backup/restore' server. I was thinking about something similar when I thought about the 'auto-update'. People seem to respond well even to the simplest of stats we put in the dashboard on c5 - so i think some exploration here makes sense. Some logs/stats? not sure if this recreates the wheel or no.

We do a fair amount of backup and sandboxing for our hosting clients, this should be as simple as 'copy' on a install list.

#DRUPAL CONSOLE SITE INSTALL MULTISITE UPGRADE#

You should be able to checkbox select /some/ installs and upgrade them to different code bases, or even downgrade. It would centralize the c5 code base, but do a lot more including. We were thinking one of these days we'd take a couple of weeks an build a standalone web server management tool. This stuff /works/ but it's hardly packaged up well or sexy. So you can still customize blocks, or even hack away, but when we do a version update to the core - it goes out everywhere.

If a client install /has/ a file in the proper place in their directory structure it will be used instead of the core's file. We have some simple scripts to create a database and the few files needed for a new client site, and then the core code base files will be used a defaults for everything else. We already have the ability to run multiple c5 installs off of a shared code base. Lemmie describe what we've got today, what we're thinking, and maybe you can help keep us on a useful track. Hey, if you read the interview, you know we're thinking about a server app to let you run many c5 installs on one machine.

Drupal console site install multisite