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

Re: Using git for code deployment on webservers?

From
TKThomas Koch <thomas@koch.ro>
Date
Jun 16, 2009, 08:01 UTC
Message-ID
<200906161001.33678.thomas@koch.ro>
In-Reply-To
<200906160111.47325.ioe-git@rameria.de>

Would it help, to share a read only GIT object store among all webservers via NFS?

Best regards, Thomas Koch
Show 46 quoted lines
> [please CC me, as I'm not subscribed]
>
> Hi there,
>
> I try to use git in a quite unusual way.
>
> I have a bunch of servers (hundreds), which get regular pulls of web
> developer code. The code consists of images, flash files, scripting
> language files, you name it. An exported repo (just the files, no SCM
> metadata) contains up to 4GB of files.
>
> No I want to distribute changes the developers made in a tree like
> structure:
>
> main server --> slave_1 --> webserver_0815
>
>             |-> slave_2 --> webserver_2342
>             |
>                         |-> webserver_4711
>
> But with the following contraints:
> - Store as little as possible on the webservers.
>   One selected revision/tag is enough.
> - Transfer as little as possible data.
>   Cancel out addition and deletion on the fly.
> - Nearly atomic update of file tree (easy to implement outside git)
>
> Nice to have:
> - Instead of copying the files to their proper names,
>   hardlink them to their git objects.
>
> At the moment I always get more data than I need and have to store
> the repository AND the checked out data.
>
> I couldn't find a way so far to get around this. Is this possible?
> Any ideas are welcome.
>
> Many Thanks in Advance!
>
> Best Regards
>
> Ingo Oeser
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Thomas Koch, http://www.koch.ro
Previous: Ingo OeserNext: Ingo Oeser
Message 4 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.