List for cgit developers and users
 help / color / mirror / Atom feed
From: hi at (hi at
Subject: Avoiding virtual-root with Nginx
Date: Sun, 6 Jan 2019 02:02:45 +0000	[thread overview]
Message-ID: <20190106020245.xcmayjocdd6lwn34@x220> (raw)

cgitrc(5) says

> NOTE: cgit has recently learned how to use PATH_INFO to achieve the
> same kind of virtual urls, so this option will probably be deprecated.

With this in mind, I've been trying and failing to set up CGit with
Nginx without using virtual-root. By default, CGit will generate links
starting with /cgit.cgi/, rather than just /, but I can set virtual-root
to / to get the behaviour I want. I've found vague mentions online of
Nginx's PATH_INFO format not being compatible with CGit, so my question
is: is this a bug in CGit, or is there something I should be doing
differently with Nginx?

Given that the quoted note is at least ten years old, I'm not worried
about it suddenly disappearing, but I'd still like to be sure I'm doing
things properly.

Alyssa Ross
hi at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <>

             reply	other threads:[~2019-01-06  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06  2:02 hi [this message]
2019-01-31 14:30 ` georg
2019-01-31 14:46   ` daniel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190106020245.xcmayjocdd6lwn34@x220 \ \

* 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).