From: Junio C Hamano <gitster@pobox•com>
To: "Jason Pyeron" <jpyeron@pdinc•us>
Cc: <git@vger•kernel.org>
Subject: Re: Advise on a push only repo
Date: Thu, 15 Jan 2015 11:31:00 -0800 [thread overview]
Message-ID: <xmqqa91j7sej.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <9782FD24F9FA45659CCE5171E73E49E7@black> (Jason Pyeron's message of "Thu, 15 Jan 2015 13:02:19 -0500")
"Jason Pyeron" <jpyeron@pdinc•us> writes:
> I am setting up a continous integration (CI) system for an open source
> project and I want to allow forking developers to use the system, but
> I do not want anyone to do a clone or fetch from the CI git repo, the
> repo.
>
> Any advice on limiting the https smart protocol to push only, blocking clone and fetch?
>
> Looking at http-backend.c
> 542 static struct service_cmd {
> ...
> 558 };
Looking at http-backend.c
19 struct rpc_service {
20 const char *name;
21 const char *config_name;
22 signed enabled : 2;
23 };
24
25 static struct rpc_service rpc_service[] = {
26 { "upload-pack", "uploadpack", 1 },
27 { "receive-pack", "receivepack", -1 },
28 };
So it would be natural to assume that there must be a way to
enable/disable these two services, no?
Looking at http_config() there, I would guess perhaps:
[http]
uploadpack = false
getanyfile = false
but I am not sure if the latter is needed (or anybody seriously
tested it, for that matter).
next prev parent reply other threads:[~2015-01-15 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 18:02 Advise on a push only repo Jason Pyeron
2015-01-15 19:31 ` Junio C Hamano [this message]
2015-01-15 22:13 ` Jason Pyeron
2015-01-15 22:24 ` Junio C Hamano
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=xmqqa91j7sej.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jpyeron@pdinc$(echo .)us \
/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