[support] Git and Multisite

[Earnie Boyd]

Earlier this year I switched hosts and am now hosting my development
sites as subhosts of the live site with dev. as the subhost.  I do not
publish this in the DNS but modify my local hosts file to map the URL
to the IP.  So I treat my development the same as my live site.  For
those who do not know and do development on a windows client the hosts
file is %WINDIR%\system32\drivers\etc\hosts on XP, I don't have
windows 7 to look there.  If I'm developing a module I can develop on
Windows, push the changes to a git repository, then pull the changes
from the git repository on the dev subhost.  Once it's ready for
production I can tag the version and pull the tagged version into the
production site.

On Wed, Mar 28, 2012 at 10:08 AM, Ms. Nancy Wichmann
<nan_wich at bellsouth.net> wrote:
> Earnie, I tend to agree with you. My live sites generally are single site
> setups, so which directory I use is not an issue. But my development sites
> on my local PC are all done in multisite, hence the problem. Taking those
> down for maintenance is not a problem since most are not even up at any
> given time. If I ever figure out Git's Auto-Deploy, this may change in the
> future.
>
> Nancy
>
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
> Jr.
>
> ________________________________
> From: Earnie Boyd
>
> I learned some time ago that it is easier for me to use
> sites/example.com/modules instead of sites/all/modules.  I simply
> cannot bring all sites down for maintenance when a module is upgraded,
> I upgrade them one at a time.
>
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]



-- 
Earnie
-- https://sites.google.com/site/earnieboyd