From: dev at famic.de (Martin M.)
Subject: Private repos & auth
Date: Thu, 13 Jun 2019 23:20:52 +0200 [thread overview]
Message-ID: <20190613212052.GB2485@remote.famic.de> (raw)
Great questions by Paul! I am facing exactly the same use case and these
questions are not yet answered:
> # Private repos
> I have my config set to "scan". Would it be possible to declare
> somewhere in the repo *itself* that it should be private?
> # Authentication
> I see the filter documentation but I am unsure how to actually implement
> it. I'd like *some* public repos but most of my repos are private.
I have recently installed Gitolite and cgit, after the usual
installation and configuration ups and downs, everything works fine now
(using SSH for cloning). But since yesterday I am struggling to
implement authentication for a subset of repos (call them private). My
first idea was to use HTTP basic auth, without success. Then I
investigated into the cgit filter and example script
'simple-authentication.lua'. I configured the variables in this script
but have no clue how to correctly trigger and deploy it. How and where
do I correctly provide the 12 arguments as mentioned in cgitrc? A
working setup using the script and proper configuration in cgitrc would
help me a lot.
There is another very interesting approach for auth using the already
provided setup from Gitolite
(https://stackoverflow.com/a/17783132/4905542). However, I could not
find the required Perl packages and put this on hold.
So, what is the best practice for using private repositories beside
public one in cgit? Any help is welcome!
next reply other threads:[~2019-06-13 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 21:20 dev [this message]
2019-06-20 21:08 ` dev
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 \
* 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).