From: Ingo Oeser <ioe-lkml@rameria.de>
To: git@vger.kernel.org, ioe-git@rameria.de
Subject: Re: Using git for code deployment on webservers?
Date: Wed, 17 Jun 2009 19:42:42 +0200 [thread overview]
Message-ID: <200906171942.43002.ioe-lkml@rameria.de> (raw)
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
next prev parent reply other threads:[~2009-06-17 17:40 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 [this message]
2009-06-16 8:01 ` Thomas Koch
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=200906171942.43002.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--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).