From: Allan Wind <allan_wind@lifeintegrity.com>
To: git@vger.kernel.org
Cc: ioe-git@rameria.de
Subject: Re: Using git for code deployment on webservers?
Date: Tue, 16 Jun 2009 03:13:28 -0400 [thread overview]
Message-ID: <20090616071328.GB6615@lifeintegrity.com> (raw)
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
next prev parent reply other threads:[~2009-06-16 7:23 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 [this message]
2009-06-17 17:42 ` Ingo Oeser
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=20090616071328.GB6615@lifeintegrity.com \
--to=allan_wind@lifeintegrity.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.