From: lekensteyn at gmail.com (Peter Wu)
Subject: FastCGI integration for cgit?
Date: Sat, 13 Apr 2013 01:51:03 -0700 (PDT) [thread overview]
Message-ID: <28484901.erkyi2NjQ4@al> (raw)
Hi all,
I am investigating the options for deploying cgit+gitolite. As I am running
nginx, I have to use fastcgi or something similar.
Some resources that I found during a search:
- http://russellhaering.com/2009/12/22/running-cgit-under-nginx/
- https://gist.github.com/stran12/1394757
- http://polemon.org/cgit_nginx
- http://blog.zx2c4.com/293
Their instructions however, do suggest the use of nginx + spawn-cgi + fcgiwrap
+ cgit. I have some issues with it:
- Even if nginx and cgit run as different users, nginx can still run arbitrary
commands under the rights of cgit (via SCRIPT_FILENAME).
- If the only goal of fcgiwrap is to run cgit, why fcgiwrap at all and not
integrate it into cgit?
So I was wondering if somebody has already considered integrating fastcgi into
cgit or other experiences with a nginx+(fastcgi+)cgit setup? I do not expect
much traffic, but still want to have a secure (isolated) setup with predictable
resource use.
Regards,
Peter
next reply other threads:[~2013-04-13 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 8:51 lekensteyn [this message]
2013-04-13 9:34 ` john
2013-04-15 14:32 ` Jason
2013-04-15 14:44 ` fcgiwrap+nginx configuration (was: Re: FastCGI integration for cgit?) lekensteyn
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=28484901.erkyi2NjQ4@al \
--to=cgit@lists.zx2c4.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).