From: Thomas Koch <thomas@koch.ro>
To: Ingo Oeser <ioe-git@rameria.de>
Cc: git@vger.kernel.org
Subject: Re: Using git for code deployment on webservers?
Date: Tue, 16 Jun 2009 10:01:33 +0200 [thread overview]
Message-ID: <200906161001.33678.thomas@koch.ro> (raw)
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
> [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
next prev parent reply other threads:[~2009-06-16 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 23:11 Using git for code deployment on webservers? Ingo Oeser
2009-06-16 7:13 ` Allan Wind
2009-06-17 17:42 ` Ingo Oeser
2009-06-16 8:01 ` Thomas Koch [this message]
2009-06-17 17:27 ` Ingo Oeser
2009-06-16 17:49 ` Daniel Barkalow
2009-06-17 17:23 ` Ingo Oeser
2009-06-17 19:26 ` Daniel Barkalow
2009-06-17 20:26 ` Alex Riesen
2009-06-17 20:33 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906161001.33678.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
--cc=ioe-git@rameria.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).