Posted by pcorbett on July 16, 2007 at 8:25pm
I have a multi-site setup where I'd like to share the system table because I want any given module to be accessible to all other sites rather than installing it for each site. Drupal doesn't allow this because to determine if you've already set up a Drupal install, it checks to see if the system table already exists (install.php line 105). Does anyone know whether bypassing this check would cause any issues? Or, is it ridiculous for me to want such functionality?
Comments
uh?
Not sure what this means - you can have a multisite module arrangement simply by having each of the modules that you want to share placed in your /sites/all/modules directory. It would seemingly make no sense to share any tables. You still have to "install" the module on a per site basis. Why on earth would you want to share that table? That would mean that you would have a forced core of modules which you couldn't "uninstall", which is pointless, because AFAIK you can just uncheck in /admin/build/modules with the setup I described and you're done...?
Web Development in Nottingham, UK by Kineta Systems / Follow me on Twitter! @NikLP
Well, all the sites on my
Well, all the sites on my multisite setup will be essentially the same save their colors and some page content. I have a single module listed in the sites/all folder, which, yes, does save me from having it duplicated. Any changes I would make to any of the sites should be mirrored on all the others (e.g, disabling a module or adding a new one). So, it would be nice in this case to activate a module and have it automatically activated on all the other sites as well (we're talking 50+ sites). It would be a pain to have to go into every site and make module changes in every one. Does that make more sense? In general, I don't think this kind of functionality is practical, but in this case it's the only way I see it working. Of course, I'm going to have to suck it up now because I believe Drupal dies with an error message if I share the system table.
reconsider
I run a multisite for myself, mainly so that I can get a feel for the pros and cons. What I get from the experience is that you often have to make a judgement call, and that is not a good ingredient for long-term pain-free experience.
You can get a school kid (or a script maybe) to update 50 sites, but you'd have to pay well to find someone to debug your multisite. Is that efficient in the long term?
So, if you are combining content/users: share tables.
Nuts and bolt config stuff, I wouldn't go there personally.