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

Re: Using git for code deployment on webservers?

From
IOIngo Oeser <ioe-lkml@rameria.de>
Date
Jun 17, 2009, 17:42 UTC
Message-ID
<200906171942.43002.ioe-lkml@rameria.de>
In-Reply-To
<20090616071328.GB6615@lifeintegrity.com>
Hi Allan,
On Tuesday 16 June 2009, Allan Wind wrote:
> 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.

No, at the moment we have built our own version of a content addressable filesystem and are distributing changes to it. We have symlinks to real file names.

I just thought, that git can do sth. similiar with its core, before trying to solve a solved problem :-)

> 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.

We do sth. similiar at the moment. De-duplication is important, because web people copy lots of data for images and flash around when doing things.

> > - Nearly atomic update of file tree (easy to implement outside git)
> 
> stow can be handy for this.
Ah! Will have a look.
Many Thanks!
Best Regards
Ingo Oeser
Previous: Allan WindNext: Thomas Koch
Message 3 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.