List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: [Idea] A local cgit configuration per project?
Date: Thu, 30 Apr 2015 14:06:18 +0100	[thread overview]
Message-ID: <20150430130618.GE16113@serenity.lan> (raw)
In-Reply-To: <CABM7q8+eeBNHXEYmBAJzUVBvqkmf4ZkvOgznSU=X2MD4kS_PvQ@mail.gmail.com>

On Thu, Apr 30, 2015 at 02:57:22PM +0200, Vincent F?rotin wrote:
> As a newbie to cgit, I'm currently trying to configure it for a a
> project which hosts some git repos.
> It seems to me (please refute me if I'm wrong) that cgit takes its
> configuration from a given hard-coded path, i.e. "/etc/cgitrc".
> This mean that basically there should only be one instance of cgit per system.
> 
> I wonder if it is feasible that cgit would take its *main*
> configuration from "/etc/cgitrc",
> but also would override it from a *local* one, e.g. a given
> configuration from a project
> (typically per Apache virtual host)?
> 
> Perhaps this could be "easily" achieved either by wrapping cgit CGI in
> an other dedicated script,
> setting a project's environment, or by cgit searching for additional
> config. pointed by an environment variable, or else through argument
> on command-line?
> 
> If this is already achievable, could you please point me to some
> related documentation?

You can set CGIT_CONFIG in the environment to override the location of
the config file.

Alternatively you can use environment variables to select a per-project
file to include with the "include" directive via macro expansion.  This
is documented in cgitrc(5) (search for "include=").


  reply	other threads:[~2015-04-30 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 12:57 
2015-04-30 13:06 ` john [this message]
2015-04-30 13:11   ` 

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=20150430130618.GE16113@serenity.lan \
    --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).