From: Alex Riesen Date: Wed, 17 Jun 2009 20:26:13 GMT Subject: Re: Using git for code deployment on webservers? Message-ID: <81b0412b0906171326y6821d511u5b93cda4a5c14458@mail.gmail.com> In-Reply-To: 2009/6/17 Daniel Barkalow : > On Wed, 17 Jun 2009, Ingo Oeser wrote: >> > Of course, the other possibility is to check out versions on the slaves, >> > and rsync that to the webservers, which is probably the optimal method if >> > you're not in a situation where you benefit from anything git does in >> > transit. >> >> I would benefit from noticing local changes. But simple rsync is what is tried now. >> Problem is, we get no de-duplication from rsync, which git could do. > > In that case, fetching trees is probably the right thing; that should give > you a point-to-point de-duplication without any history (although you may > also turn up git bugs, since this isn't how git is normally used). Or, you can just keep a namespace for each server in the intermediate repositories, which records the version the server has and the version it should have. Then you can use git diff-tree to find you which files have to be transferred. You wont be able to record changes on the servers, though.