All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Ingo Oeser <ioe-git@rameria.de>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: Using git for code deployment on webservers?
Date: Wed, 17 Jun 2009 22:26:13 +0200	[thread overview]
Message-ID: <81b0412b0906171326y6821d511u5b93cda4a5c14458@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0906171328080.2147@iabervon.org>

2009/6/17 Daniel Barkalow <barkalow@iabervon.org>:
> On Wed, 17 Jun 2009, Ingo Oeser wrote:
>> > Of course, the other possibility is to check out versions on the slaves,
>> > and rsync that to the webservers, which is probably the optimal method if
>> > you're not in a situation where you benefit from anything git does in
>> > transit.
>>
>> I would benefit from noticing local changes. But simple rsync is what is tried now.
>> Problem is, we get no de-duplication from rsync, which git could do.
>
> In that case, fetching trees is probably the right thing; that should give
> you a point-to-point de-duplication without any history (although you may
> also turn up git bugs, since this isn't how git is normally used).

Or, you can just keep a namespace for each server in the intermediate
repositories, which records the version the server has and the version
it should have. Then you can use git diff-tree to find you which files
have to be transferred. You wont be able to record changes on the servers,
though.

  reply	other threads:[~2009-06-17 20:26 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
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 [this message]
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=81b0412b0906171326y6821d511u5b93cda4a5c14458@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=barkalow@iabervon.org \
    --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.