I have a live site running for a university program on their server and I am maintaining a mirror image dev site on my local box. I set Drupal up as multisite for both dev and live. Apache/mysql/windows ---> environment
Now, I have a situation where another developer must create and add a new section for their program within my live site. He wants to use modules that I'm not using. And he wants to maintain a dev site for his work on his local box. There is no separate domain for his section. He will be using my theme. My domain is: http://water.uidaho.edu I have a sites folder named "water" on the dev and live site. He will be locating his section at http://water.uidaho.edu/hisprogramname
So, hmmm.
I am imagining the horror of keeping two development sites current.
Thinking is getting clogged up on how I can use multisite to solve this problem. I'd like to him to have his own database and his own sites folder.
Need someone to discuss this with. Anybody out there?
Comments
if you use 'standard'
if you use 'standard' multisite installation you can have different databases for each of your sites... and as for the folders you can create a modules folder inside your 'sites/water.uidaho.edu.hisprogramname' folder so that the modules available to his site can not be seen on other sites.
I have a multisite instalation for 10 sites... and i use different modules for each of them, the only thing is that i use shared tables to share the users between sites... but it should work well... and I have other 2 sites that I use for development...
to ease my work I made some shell scripts (I use Linux hosting) to copy module folders, update modules, modify file permissions and 'bulk' updates... and stuff like that... i'm using Linux but it can be done from win using .bat files.
even so using scripts, it's hard to keep everything up and running... it's a time consuming process. But in the end, when you look back at what you have done... you'll be proud of your self (lovely feeling)...
I'd find the ones that you
I'd find the ones that you have in common and put them in the sites/all/modules folder. Then create a folder in the multisite that's specifically for him and give him server access to drop new modules into sites/his.address/modules. We do this all the time and then you don't need to worry about HIS site screwing with yours because it's essentially a segregated environment from yours. Do it all the time with "live" and "dev" sites essentially living side by side because their dbs and parts of code base are totally separate. He might be able to down his own site but he aint downing yours.
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
Note that before you move
Note that before you move modules or themes into a different directory, you want to disable them on the site first. Don't uninstall them (by using the Uninstall tab on the modules list page), as that will delete the data associated with them; just disable them by going to the Modules list and unticking their check boxes. Once a module is disabled, you can move it to a different directory and then re-enable it in the modules list, and you should have all your data back at that point.
The Boise Drupal Guy!