git multisite setup

git multisite setup

[Matt Di Pasquale]

Hi,
In my sites folder i have folders for different sites of mine:
example.com example2.com, and i also have generic files like an
includes dir and a .htaccess file that all sites use. what is the best
way to track the generic files and the different sites?

i was thinking each site has its own .git repo. and then make a .git
repo for my sites folder but ignore the individual sites dirs.
actually that's what i'm doing now.

should i use submodules? i don't really understand submodules and the
examples i saw did not cover nested folders

Thanks!

matt

Re: git multisite setup

[Nicolas Sebrecht]

The 16/11/09, Matt Di Pasquale wrote:

> In my sites folder i have folders for different sites of mine:
> example.com example2.com, and i also have generic files like an
> includes dir and a .htaccess file that all sites use. what is the best
> way to track the generic files and the different sites?
> 
> i was thinking each site has its own .git repo. and then make a .git
> repo for my sites folder but ignore the individual sites dirs.
> actually that's what i'm doing now.

This looks good to me. Why would you like to change?

-- 
Nicolas Sebrecht

Re: git multisite setup

[Matt Di Pasquale]

yeah. i guess it's fine. :) just that the specific git repos aren't
coordinated to the generic one. but that's fine so far since i haven't
had to jump around to different commits and the generic has stayed
pretty much the same.

On Mon, Nov 16, 2009 at 7:13 PM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> wrote:
> The 16/11/09, Matt Di Pasquale wrote:
>
>> In my sites folder i have folders for different sites of mine:
>> example.com example2.com, and i also have generic files like an
>> includes dir and a .htaccess file that all sites use. what is the best
>> way to track the generic files and the different sites?
>>
>> i was thinking each site has its own .git repo. and then make a .git
>> repo for my sites folder but ignore the individual sites dirs.
>> actually that's what i'm doing now.
>
> This looks good to me. Why would you like to change?
>
> --
> Nicolas Sebrecht
>

Re: git multisite setup

[Nicolas Sebrecht]

[ Please, don't top-post nor whole quote. ]

The 16/11/09, Matt Di Pasquale wrote:

>                                       the specific git repos aren't
> coordinated to the generic one. but that's fine so far since i haven't
> had to jump around to different commits and the generic has stayed
> pretty much the same.

I'm not sure to understand exactly what kind of coordination you expect
exactly (because you don't describe what you'd like that much), but
submodule could be what you need, yes.

FMHO, the best way to check if you need it is to try it. For a good
start, I guess you'll need to change your approach on "what depends of
what". I think you should consider the _common_ part to be the
_dependency_; as a consequence, it should be the submodule used in the
other repositories. AFAIR, submodule was originaly designed to make our
life easier with libraries. It may fit to your needs too but again, the
best thing to do is to try.

-- 
Nicolas Sebrecht