From: Avery Pennarun <apenwarr@gmail.com>
To: matvejchikov@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Is it possible to use git as a remote file storage without making any local repos?
Date: Wed, 28 Oct 2009 14:33:34 -0400 [thread overview]
Message-ID: <32541b130910281133nf79e03fy208b7f9fdb86bd05@mail.gmail.com> (raw)
In-Reply-To: <8496f91a0910280509p49447d6egd7c07b382657c375@mail.gmail.com>
On Wed, Oct 28, 2009 at 8:09 AM, Matvejchikov Ilya
<matvejchikov@gmail.com> wrote:
> I have a remote storage server with a git-daemon running and I want to
> be able to put some data in that repo
> in a way like 'git hash-object -w <object>'. The general problem for
> me is that I don't want to create any local
> git repositories that is needed by 'pit push ...' etc.
>
> So, is it possible to use git for remote storage purposes without
> making local repository?
This functionality isn't built into git (and it might be considered a
security hole, strictly speaking, if a repository let you download any
object by default). However, it would be pretty easy to create your
own server that does this.
For example, you could make one CGI script that dumps its POST data
into a pipe to "git hash-object --stdin -w"
I've written a service similar to this at work. It's relatively
simple to do a basic version. Of course, as you get into more
complicated situations (what about multiple users updating the same
filename? merges? authentication?) it gets more complicated. But I
think everybody would want this for a different reason, so it's
unlikely that there'll ever be a single "standard" solution.
Have fun,
Avery
prev parent reply other threads:[~2009-10-28 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 12:09 Is it possible to use git as a remote file storage without making any local repos? Matvejchikov Ilya
2009-10-28 18:33 ` Avery Pennarun [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=32541b130910281133nf79e03fy208b7f9fdb86bd05@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=matvejchikov@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).