git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Using git for code deployment on webservers?

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jun 17, 2009, 20:26 UTC
Message-ID
<81b0412b0906171326y6821d511u5b93cda4a5c14458@mail.gmail.com>
In-Reply-To
<alpine.LNX.2.00.0906171328080.2147@iabervon.org>
2009/6/17 Daniel Barkalow <barkalow@iabervon.org>:
Show 12 quoted lines
> 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.

Previous: Daniel BarkalowNext: Alex Riesen
Message 9 of 10 in “Using git for code deployment on webservers?”
  1. Ingo OeserJun 15, 2009
  2. Allan WindJun 16, 2009
  3. Ingo OeserJun 17, 2009
  4. Thomas KochJun 16, 2009
  5. Ingo OeserJun 17, 2009
  6. Daniel BarkalowJun 16, 2009
  7. Ingo OeserJun 17, 2009
  8. Daniel BarkalowJun 17, 2009
  9. Alex RiesenJun 17, 2009
  10. Alex RiesenJun 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.