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.
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.
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/ ]
On Tue, 2012-03-27 at 06:46 -0700, Ms. Nancy Wichmann 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.
You could use a git branch that you and your friend agreed to as the assumed master branch. For example collab1 branch that contains only the needed modules. You could start the branch from first commit, and build the content using git cherry-pick.
Maybe add another collab1-dev branch or something.
fireh.
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.
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.
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@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 Boyd -
Fahri Reza -
Ms. Nancy Wichmann -
Todd Bloom