Git and multisite: mutually exclusive?
I've been racking my brain trying to come up with an elegant git workflow for multisite. If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level. Has anyone found a nice way to handle this? --- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder
Can't really understand form this message what you are hung up on? Asside from needed cutsomizations to .gitignore there's nothing really different about multisite vs. non-multisite in code base. What specifically are you having trouble with? Dave From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jeff Greenberg Sent: Wednesday, November 27, 2013 7:00 AM To: support@drupal.org Subject: [support] Git and multisite: mutually exclusive? I've been racking my brain trying to come up with an elegant git workflow for multisite. If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level. Has anyone found a nice way to handle this? --- drupal.org/user/367108<http://drupal.org/user/367108> linkedin.com/in/jeffrgreenberg<http://linkedin.com/in/jeffrgreenberg> accidentalcoder.com<http://accidentalcoder.com> / ayendesigns.com<http://ayendesigns.com> @accidentalcoder
sorry, I didn't specify the multisite use. So, 4 domains sharing one codebase. Each of those domains will be pulling files that should only have the core files and their site files, but not the other site files.
On Nov 27, 2013, at 11:35 AM, "Metzler, David" <metzlerd@evergreen.edu> wrote:
Can’t really understand form this message what you are hung up on? Asside from needed cutsomizations to .gitignore there’s nothing really different about multisite vs. non-multisite in code base. What specifically are you having trouble with?
Dave
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jeff Greenberg Sent: Wednesday, November 27, 2013 7:00 AM To: support@drupal.org Subject: [support] Git and multisite: mutually exclusive?
I've been racking my brain trying to come up with an elegant git workflow for multisite.
If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level.
Has anyone found a nice way to handle this?
--- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder -- [ Drupal support list | http://lists.drupal.org/ ]
Jeff, I build another repo for the multisite core. Of course, it excludes the sites. As far as I am concerned, the core part is an entity that is managed separately from the individual sites. Nancy
________________________________ From: Jeff Greenberg <listmail.ayendesigns@gmail.com> To: "support@drupal.org" <support@drupal.org> Sent: Wednesday, November 27, 2013 9:59 AM Subject: [support] Git and multisite: mutually exclusive?
I've been racking my brain trying to come up with an elegant git workflow for multisite.
If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level.
Has anyone found a nice way to handle this?
--- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder -- [ Drupal support list | http://lists.drupal.org/ ]
Nancy, do you have nested checkouts then or did you need to build a script to manage the combining of the sites checkout with the core checkout? Does this work then? : .gitignore of the core site includes sites but then you create a checkout of the separate repo in the sites folder with its own .gitignore file? Curious as well. From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Wednesday, November 27, 2013 9:23 AM To: support@drupal.org Subject: Re: [support] Git and multisite: mutually exclusive? Jeff, I build another repo for the multisite core. Of course, it excludes the sites. As far as I am concerned, the core part is an entity that is managed separately from the individual sites. Nancy ________________________________ From: Jeff Greenberg <listmail.ayendesigns@gmail.com<mailto:listmail.ayendesigns@gmail.com>> To: "support@drupal.org<mailto:support@drupal.org>" <support@drupal.org<mailto:support@drupal.org>> Sent: Wednesday, November 27, 2013 9:59 AM Subject: [support] Git and multisite: mutually exclusive? I've been racking my brain trying to come up with an elegant git workflow for multisite. If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level. Has anyone found a nice way to handle this? --- drupal.org/user/367108<http://drupal.org/user/367108> linkedin.com/in/jeffrgreenberg<http://linkedin.com/in/jeffrgreenberg> accidentalcoder.com<http://accidentalcoder.com/> / ayendesigns.com<http://ayendesigns.com/> @accidentalcoder -- [ Drupal support list | http://lists.drupal.org/ ]
Hi May be you need to use drush make to build an installation profile, I think this help you build what you need. This tool allows you to have setup sites without needing to have third party hosted code, such as core in your repo. There Are several posts about this at Drupal.org and from other sources. -- Felix
On Nov 27, 2013, at 12:28 PM, "Metzler, David" <metzlerd@evergreen.edu> wrote:
Nancy, do you have nested checkouts then or did you need to build a script to manage the combining of the sites checkout with the core checkout?
Does this work then? :
.gitignore of the core site includes sites but then you create a checkout of the separate repo in the sites folder with its own .gitignore file?
Curious as well.
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Wednesday, November 27, 2013 9:23 AM To: support@drupal.org Subject: Re: [support] Git and multisite: mutually exclusive?
Jeff, I build another repo for the multisite core. Of course, it excludes the sites. As far as I am concerned, the core part is an entity that is managed separately from the individual sites.
Nancy
From: Jeff Greenberg <listmail.ayendesigns@gmail.com> To: "support@drupal.org" <support@drupal.org> Sent: Wednesday, November 27, 2013 9:59 AM Subject: [support] Git and multisite: mutually exclusive?
I've been racking my brain trying to come up with an elegant git workflow for multisite.
If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level.
Has anyone found a nice way to handle this?
--- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
To my thinking, having core in the repo isn't just a matter if deploying core to the local box, otherwise the drush build would be fine, as you suggest. It's also a matter of files being added to sites/all/modules, sites/all/libraries, etc. If one could be certain that they would always be changed at the server end, redeploying via drush could work, but what if the files are added at the local end?
On Nov 27, 2013, at 6:01 PM, Fxarte <fxarte@gmail.com> wrote:
Hi May be you need to use drush make to build an installation profile, I think this help you build what you need. This tool allows you to have setup sites without needing to have third party hosted code, such as core in your repo. There Are several posts about this at Drupal.org and from other sources.
-- Felix
On Nov 27, 2013, at 12:28 PM, "Metzler, David" <metzlerd@evergreen.edu> wrote:
Nancy, do you have nested checkouts then or did you need to build a script to manage the combining of the sites checkout with the core checkout?
Does this work then? :
.gitignore of the core site includes sites but then you create a checkout of the separate repo in the sites folder with its own .gitignore file?
Curious as well.
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Nancy Wichmann Sent: Wednesday, November 27, 2013 9:23 AM To: support@drupal.org Subject: Re: [support] Git and multisite: mutually exclusive?
Jeff, I build another repo for the multisite core. Of course, it excludes the sites. As far as I am concerned, the core part is an entity that is managed separately from the individual sites.
Nancy
From: Jeff Greenberg <listmail.ayendesigns@gmail.com> To: "support@drupal.org" <support@drupal.org> Sent: Wednesday, November 27, 2013 9:59 AM Subject: [support] Git and multisite: mutually exclusive?
I've been racking my brain trying to come up with an elegant git workflow for multisite.
If I just want the site portions under git control, then it's not an issue. But if I want core as part of each, then it becomes so. I considered using git submodule, but then the workflow gets more complex on the local level.
Has anyone found a nice way to handle this?
--- drupal.org/user/367108 linkedin.com/in/jeffrgreenberg accidentalcoder.com / ayendesigns.com @accidentalcoder
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
participants (4)
-
Fxarte -
Jeff Greenberg -
Metzler, David -
Nancy Wichmann