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:33:37 +0200 [thread overview]
Message-ID: <81b0412b0906171333l38b1c2e0y2e166bc0ae7a461d@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0906171326y6821d511u5b93cda4a5c14458@mail.gmail.com>
2009/6/17 Alex Riesen <raa.lkml@gmail.com>:
> Or, you can just keep a namespace for each server in the intermediate
I mean namespace of branches:
refs/heads/webserver_1/master (current)
refs/heads/webserver_1/next (to be updated to)
> 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.
Something like that:
git diff-tree --diff-filter=AM webserver1_/master..webserver_1/next |
while read f; do scp "$f" webserver_1:"$f" || break; done
git diff-tree --diff-filter=D webserver1_/master..webserver_1/next |
while read f; do ssh webserver_1 rm -f "$f" || break; done
prev parent reply other threads:[~2009-06-17 20:33 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
2009-06-17 20:33 ` Alex Riesen [this message]
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=81b0412b0906171333l38b1c2e0y2e166bc0ae7a461d@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 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).