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

Re: Using git for code deployment on webservers?

From
AWAllan Wind <allan_wind@lifeintegrity.com>
Date
Jun 16, 2009, 07:13 UTC
Message-ID
<20090616071328.GB6615@lifeintegrity.com>
In-Reply-To
<200906160111.47325.ioe-git@rameria.de>
On 2009-06-16T01:11:47, Ingo Oeser wrote:
> - Transfer as little as possible data.
>   Cancel out addition and deletion on the fly.

I use `git diff` with the post-receive hook to distribute changes to my web server. diff carries the previous content when you delete a file, and in my case this was large mpeg files defeating the purpose somewhat.

If you do not mind having a full repository on the web servers, then pushing changes might work better. This appears to be what you are doing now though.

If I had to scale this I would probably build a master image (either locally or remotely) and use rsync to distribute the content instead of git.

> - Nearly atomic update of file tree (easy to implement outside git)
stow can be handy for this.
/Allan
-- 
Allan Wind
Life Integrity, LLC
http://lifeintegrity.com
Previous: Ingo OeserNext: Ingo Oeser
Message 2 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.