1

I am working on a project where I have a basic site with a sets of modules and configurations. Currently when I get a new client for this project in order for him/her to use their own site, I setup a subdomain, load a basic DB and copy the basic site files over.

This setup has work for me, but now I am having to deal with more clients and the manual process will just make it hard to manage and maintain. Ideally I will love to have it a single set of files will connect each user DB and I don't care if instead of subdomains (they are nicer) I have to use sub-directories.

What will be best for this setup multisite or multiple sites, and will it make sense to have a centralize account (open id) server?

Note: I was thinking in register the users in a single place and then they can login into their private sites using this centralize account system. Otherwise each site will have to have a user 1 account with a password to be manage for each site.

Thank you

  • Will each sub-site need it's own user base or just the client admin account? – Darvanen Jan 14 '15 at 23:09
1

I use multisite to run about 50 Drupal sites from a single code base, but each site has its own database.

To be able to manage all the site, I use the Drupal Remote Dashboard Server module and its corresponding Drupal Remote Dashboard module. These modules let me out all the servers into maintenance mode, or run update.php.

| improve this answer | |
  • Does each site has a user 1 plus any other user or do you use something like Open ID to have a centralize account directory? Do you have modules in one of the sites that you don't use in another? – Emil Orol Jan 16 '15 at 13:47
  • Each site has its own User1 (me), but the Drupal Remote Dashboard Server module take care of logging you in to them all. Each site has its own set of modules, installed into its /site/sitename.com/modules directory. – iantresman Jan 16 '15 at 15:16
  • Do you share any tables between the site databases? Do you have the sites as sub domains or directories of the main site? – Emil Orol Jan 16 '15 at 23:40
  • Each site has its own database, to ensure data integrity. Each site has its own full domain. – iantresman Jan 18 '15 at 0:34
1

I think multisite would work well if you're keeping all of the same code. I know you can do it with subdomains (or even completely different domains) using the sites.php file, I'm not so sure about sub-directories.

Have a look at the Features module which will allow you to import all of your standard settings as a single module on new sites.

| improve this answer | |
  • Thank you for your quick answer. I have been avoiding Features like the plague waiting for the file configuration system on D8 and/or Backdrop. – Emil Orol Jan 14 '15 at 22:34
  • That's what I have right now a basic site with the modules and the DB configuration that I copy over the newly created subdomain. The question about Open ID is just to learn if it will make sense or not to use it with such setup. – Emil Orol Jan 14 '15 at 22:45
  • I was thinking in register the users in a single place and then they can login into their private sites using this centralize account system. Otherwise each site will have to have a user 1 account with a password to be manage. – Emil Orol Jan 14 '15 at 22:51
  • Best update your question with that, people might miss it in the comments =) – Darvanen Jan 14 '15 at 22:52
  • Good point. I just did that. Once again, thank you. – Emil Orol Jan 14 '15 at 22:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.