On Tue, Mar 27, 2012 at 9:46 AM, Ms. Nancy Wichmann nan_wich@bellsouth.net wrote:
I'm going to guess that I know the answer already.
I have a friend who wants to collaborate on a pro-bono site I am developing. So I thought of creating a repository on GitHub to make it easier. But I do all my development in a true multisite (single code base). So, for example, sites/all/modules contains every module that any of my sites uses. This is far more than this particular site uses.
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.
If I build a repository, is it not going to contain all those modules (themes, images, etc) even though they are not needed for this site? Do I need to split it off to a single site with only the modules (etc.) that are needed for that one site?
Yes, this is what I would do if I were you.
I think building and maintaining a .gitignore file would be far more annoying than splitting the site.
Ditto.