Petr Baudis [off-list ref] writes:
yes, you can push using HTTP DAV - just push to an HTTP URL; make sure
you have git-http-push compiled, it is sometimes not compiled because it
unfortunately adds dependencies on couple of more libraries.
That's great. I don't need this right now, but having worked behind a
firewall + proxy, I know how appreciable it is to push with DAV ;-).
I think a patch that would add support for pushing over sftp or some
other dumb protocol would be welcome. One problem is with proper locking
of ref updates (not sure how well would sftp cope with that), another is
that you will need to do git-update-server-info's job on the server
side.
It should be possible (but not implemented AAUI) also to generate the
additional info of git-update-server-info on the client, isn't it?
If you already have SSH access to the server, why not compile Git
there and install it to your $HOME, though?
I'll probably do, but my concern is broader than that. I like the
ability to use almost any webhosting service for my revision control.
GNU Arch was quite good at that, bzr is also (doesn't support webdav
very well yet, but read-only-HTTP, sftp and ftp are there), so I'd
like git to do the same.
And yes, there are tons of reasons not to install git on the server.
In particular, the fact that I'm not root there, and too lazy to do
more than "aptitude install git" with pleasure ;-).
--
Matthieu Moy wrote:
I'll probably do, but my concern is broader than that. I like the
ability to use almost any webhosting service for my revision control.
GNU Arch was quite good at that, bzr is also (doesn't support webdav
very well yet, but read-only-HTTP, sftp and ftp are there), so I'd
like git to do the same.
Well, git can fetch (read) via http, https, ftp, sftp, rsync, git, ssh+git;
it can push via http(s) with WebDAV, and ssh+git (ssh+git meaning via ssh,
with git installed on the server side).
BTW. rsync is considered obsolete, and suitable only for initial cloning,
perhaps.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
On Thu, 2 Nov 2006, Matthieu Moy wrote:
I'll probably do, but my concern is broader than that. I like the
ability to use almost any webhosting service for my revision control.
GNU Arch was quite good at that, bzr is also (doesn't support webdav
very well yet, but read-only-HTTP, sftp and ftp are there), so I'd
like git to do the same.
You should be able to put together the repository you want hosted locally
and use any webhosting service updating procedure to update what's hosted.
AFAIK, git.kernel.org is a completely dumb mirror of master.kernel.org,
working like that.
The main thing is that you want "objects" to be updated before "refs", and
you don't want to do any git operations during the mirroring. But it's not
even that important, so long as whenever you leave the mirror for a while,
it matches some final state (with respect to git) of the master.
What you actually care about the git-native stuff for is preparing the
master image, so that you don't have random cruft from your working
repository, and then you just want it to mirror efficiently.
-Daniel
Dear diary, on Thu, Nov 02, 2006 at 01:04:16PM CET, I got a letter
where Matthieu Moy [off-list ref] said that...
Petr Baudis [off-list ref] writes:
quoted
I think a patch that would add support for pushing over sftp or some
other dumb protocol would be welcome. One problem is with proper locking
of ref updates (not sure how well would sftp cope with that), another is
that you will need to do git-update-server-info's job on the server
side.
It should be possible (but not implemented AAUI) also to generate the
additional info of git-update-server-info on the client, isn't it?
Yes, that's what git-http-push does.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1