[support] Git and multisite: mutually exclusive?

[Jeff Greenberg]

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 at 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 at 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 at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Nancy Wichmann
>> Sent: Wednesday, November 27, 2013 9:23 AM
>> To: support at 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 at gmail.com>
>> To: "support at drupal.org" <support at 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/ ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20131127/336c93b0/attachment-0001.html