From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Ben Mezger <me@benmezger.nl>, git@vger.kernel.org
Subject: Re: Git Smart HTTP using Nginx
Date: Thu, 10 Mar 2016 15:07:14 +0100 [thread overview]
Message-ID: <1457618834.11765.12.camel@kaarsemaker.net> (raw)
In-Reply-To: <56E1730D.4030603@benmezger.nl>
On do, 2016-03-10 at 10:13 -0300, Ben Mezger wrote:
> The git-scm.com only uses apache2 as an example of setting Git's
> Smart
> HTTP, and searching the web for the Nginx's config only gives me old
> configs or not-functional configurations. Has anyone managed to get
> Smart HTTP to work with Nginx and could give me a sample of the
> .conf?
This works for me, using fcgiwrap:
location ~ ^.*/(HEAD|info/refs|objects/info/.*|git-(upload|receive)-pack)$ {
fastcgi_pass unix:/var/run/fcgiwrap.socket;
fastcgi_param SCRIPT_FILENAME /usr/lib/git-core/git-http-backend;
fastcgi_param PATH_INFO $uri;
fastcgi_param GIT_PROJECT_ROOT $repo_root;
fastcgi_param REMOTE_USER $remote_user;
include fastcgi_params;
}
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
prev parent reply other threads:[~2016-03-10 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:13 Git Smart HTTP using Nginx Ben Mezger
2016-03-10 14:07 ` Dennis Kaarsemaker [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=1457618834.11765.12.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=me@benmezger.nl \
/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).