From: Martin Langhoff <martin.langhoff@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "René Moser" <mail@renemoser.net>,
"Timo Besenreuther" <timo.besenreuther@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-ftp: retry, sftp support
Date: Mon, 18 Jul 2011 04:09:59 -0400 [thread overview]
Message-ID: <CACPiFCK4B96cTAz8JEBMOpktZG2R5HsYA2YgEdRuqO55XTOVcg@mail.gmail.com> (raw)
In-Reply-To: <m3vcv0yqb4.fsf@localhost.localdomain>
2011/7/18 Jakub Narebski <jnareb@gmail.com>:
> Martin Langhoff <martin.langhoff@gmail.com> writes:
>
>> René, Timo,
>>
>> Thanks for git-ftp -- it has saved me from going crazy with low cost
>> hosting setups that only support ftp.
>
> Could you give us a link? It isn't in git core, is it?
git remote -v
origin git://github.com/BeezyT/git-ftp.git (fetch)
origin git://github.com/BeezyT/git-ftp.git (push)
> How git-ftp differs from ftp / ftps remote helper (git-remote-ftp etc.)?
AIUI, the ftp/ftps remote helpers are to keep a git _repo_ on a server
that runs ftp.
This git-ftp is a "deploy the tip of my branch onto a production
server" tool. The usage model is
- hack on your html/php website on your dev machine, in a git checkout
- commit your code
- use git-ftp to publish to the hosting server
Maybe it should be called "git ftpdeploy". It's a handy trick. I
found it via http://stackoverflow.com/questions/2950107/git-push-into-production-ftp
m
--
martin.langhoff@gmail.com
martin@laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2011-07-18 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 2:35 git-ftp: retry, sftp support Martin Langhoff
2011-07-18 7:57 ` Jakub Narebski
2011-07-18 8:09 ` Martin Langhoff [this message]
2011-07-18 8:58 ` Timo Besenreuther
2011-07-18 10:51 ` Martin Langhoff
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=CACPiFCK4B96cTAz8JEBMOpktZG2R5HsYA2YgEdRuqO55XTOVcg@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=mail@renemoser.net \
--cc=timo.besenreuther@gmail.com \
/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).