From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason at zx2c4.com (Jason A. Donenfeld)
Date: Tue, 30 Oct 2012 10:29:16 -0600
Subject: [PATCHv3 1/3] Add config option user-envvar
In-Reply-To: <1351591890-13605-2-git-send-email-valentin.haenel@gmx.de>
References: <1350378927-10834-1-git-send-email-valentin.haenel@gmx.de>
 <1351591890-13605-2-git-send-email-valentin.haenel@gmx.de>
Message-ID: <CAHmME9q=tcb9TD8cFPh+Cf3vWq5puTiQdm5Kw7qdP246Sd5=bQ@mail.gmail.com>

On Tue, Oct 30, 2012 at 4:11 AM, Valentin Haenel <valentin.haenel at gmx.de> wrote:
> When cgit sits on a backend server and relies on a set of
> front-ends to do authentication, it will read the username
> from an environment variable defined by this option.
>
> In this way, one can safely use any forwarded HTTP header
> and not only the expected REMOTE_USER variable set by the
> CGI standard.
>

As I wrote in another email, this isn't necessary, and I don't dig the
extra book keeping. The helper script can manage all this using normal
environment variables that are inherited.

In fact, as I also explained before, instead of positional arguments,
everything can be passed in env vars. In fact, quite a few CGIT_* env
vars are already defined.