Yes, the modules that are used are in sites/all/modules. But not everything in that directory is used; there are many modules in there that are not used on this particular site (as well as themes, etc.).
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Todd Bloom todd.bloom@me.com To: support@drupal.org Sent: Tuesday, March 27, 2012 9:59 AM Subject: Re: [support] Git and Multisite
Will you be using any modules from your "/sites/all/" directory?
If you won't, then could you just initialize a new repository in your /sites/thedomain.com folder?
There's also the possibility of using Git submodules, though I don't really have experience with them so I'm not entirely certain if they would apply to this type of situation.
http://book.git-scm.com/5_submodules.html
Regards, Todd
On Mar 27, 2012, at 09: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.
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?
I think building and maintaining a .gitignore file would be far more annoying than splitting the site. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr. -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]