Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Sunshiney on
Yesterday I learned that another developer is going to be converting his FP site to Drupal and folding it into my university program's live Drupal site. I've been the solo developer of our site. He wants to maintain his own dev site on his local machine. I have my own dev site on my local machine. While some of his visitors/users will overlap with mine, he has users who have no use for the rest of our site (e.g. school teachers and high school students who will only use some of his pages). He will need modules dif from mine.
So, I tossed and turned last night about the concept of maintaining two dev sites and one production site. And about registration log-ins, but that's probably the easier of the two problems.
Looking for conversation / thoughts on this... Would you maintain two dev sites? if not, how to keep them current? I have the dev and prod. site set up using multisite...and wondering if there's an alternative before we get two far into this. Hmmm... wondering what's the best way to handle this new developer and his needs.
Comments
=-=
personally, I'd consider a multisite install which will allow the other developer to use the module he/she wants. You can shared logins and sessions. If the other side of the site is radically different consider a subdomain.
more info on how to set up a multisite and how to share users and sesssions and the like, without the need for a module when sites are on teh same server using separate databases = http://www.slideshare.net/jvandyk/multisite-van-dyk-walkah-presentation
Actually, both my dev and
Actually, both my dev and prod sites are already config'd as multisite. One core, one database for each site. What do you mean by share "sessions." We'll both use same custom theme I created; it's just that he's dealing with a grant program that is part of our larger program. His current site is in a folder off our old FP site. So he and powers above want the same path ... http://mydomain.domain.edu/hisfolderandsubdirectories..
I've used multisite for uniquely dif sites. But is it possible to use multisite for what I've described above?
Thanks for that link. Any other links that could help with this problem??
=-=
sessions are what happens when a user logins in. Essentially regardless of what side of the site a user logs in on, they remain logged in when traveling from site to site. Walking through the screencast presentation should present a better understanding of this.
multisite can be used for what you describe, yes.
Theme would go in sites/all/themes, to be shared by both sites
Modules to be shared by both sites in sites/all/modules
modules specific to your site in sites/yoursite.com/modules
modules specific to his modules in sites/hissite.com/modules
I dislike sites in subdirectories so I haven't studied it much but it can be done and I believe there is documentation on that type of set up in the documentation area and found through out the forums in previous threads. I'd push for hissite.thedomain.edu to be set up on the server with the doc root pointing to the main codebase which I find far easier to work with then dealing with subdirectory installations.
Ok... looked at
Ok... looked at screencast... I find it harder to follow slideshows without audio. So, essentially, I'll just have a path at my site that links to his so it'll look transparent to end user. Interesting.