From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jeff King <peff@peff•net>
Cc: Ethan Reesor <firelizzard@gmail•com>,
Konstantin Khomoutov <kostix+git@007spb•ru>,
git <git@vger•kernel.org>
Subject: Re: Pushing a git repository to a new server
Date: Wed, 13 Feb 2013 09:08:36 +0100 [thread overview]
Message-ID: <511B4A04.1000104@drmicha.warpmail.net> (raw)
In-Reply-To: <20130212204210.GA25330@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 12.02.2013 21:42:
> On Tue, Feb 12, 2013 at 12:28:53PM +0100, Michael J Gruber wrote:
>
>> I'm not sure providers like GitHub would fancy an interface which allows
>> the programmatic creation of repos (giving a new meaning to "fork
>> bomb"). But I bet you know better ;-)
>
> You can already do that:
>
> http://developer.github.com/v3/repos/#create
Nice.
I knew you knew ;)
> We rate-limit API requests, and I imagine we might do something similar
> with create-over-git. But that is exactly the kind of implementation
> detail that can go into a custom create-repo script.
>
>> An alternative would be to teach git (the client) about repo types and
>> how to create them. After all, a repo URL "ssh://host/path" gives a
>> clear indication that "ssh host git init path" will create a repo.
>
> But that's the point of a microformat. It _doesn't_ always work, because
> the server may not allow arbitrary commands, or may have special
> requirements on top of the "init". You can make the microformat be "git
> init path", and servers can intercept calls to "git init" and translate
> them into custom magic. But I think the world is a little simpler if we
> define a new service type (alongside git-upload-pack, git-receive-pack,
> etc), and let clients request it. Then it's clear what the client is
> trying to do, it's easy for servers to hook into it, we can request it
> over http, etc. And it can be extended over time to take more fields
> (like repo description, etc).
>
> I'm really not suggesting anything drastic. The wrapper case for ssh
> would be as simple as a 3-line shell script which calls "git init" under
> the hood, but it provides one level of indirection that makes
> replacing/hooking it much simpler for servers. So the parts that are in
> stock git would not be much work (most of the work would be on _calling_
> it, but that is the same for adding a call to "git init").
>
> I think the main reason the idea hasn't gone anywhere is that nobody
> really cares _that_ much. People just don't create repositories that
> often. I feel like this is one of those topics that comes up once a
> year, and then nothing happens on it, because people just make their
> repo manually and then stop caring about it.
>
> Just my two cents, of course. :)
Most repos are probably created by a local "git init" or "git clone", or
by clicking a button on a provider's web interface. The need for
git-create-repo seems to be restricted to:
- "command line folks" who use a provider for it's hosting service and
don't fancy a web interface for repo creation
- noobs who need to get their head wrapped around local, remote,
push/pull 'n' stuff...
For the server side git-create-repo to take off we would probably need
two things (besides the client support):
- Implement and ship a git-create-repo which makes this work for git
over ssh seamlessly. (Will take some to trickle down to servers in the
wild.)
- Get a large provider to offer this.
Gitosis/Gitolite are probably to follow easily. I'm beginning to like
idea ;)
Michael
prev parent reply other threads:[~2013-02-13 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 21:00 Pushing a git repository to a new server Ethan Reesor
2013-02-11 7:50 ` Konstantin Khomoutov
2013-02-11 7:57 ` Ethan Reesor
2013-02-11 12:45 ` Konstantin Khomoutov
2013-02-11 18:18 ` Ethan Reesor
2013-02-11 16:27 ` Jeff King
2013-02-11 18:17 ` Ethan Reesor
2013-02-12 11:28 ` Michael J Gruber
2013-02-12 20:42 ` Jeff King
2013-02-13 8:08 ` Michael J Gruber [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=511B4A04.1000104@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=firelizzard@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=kostix+git@007spb$(echo .)ru \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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