From: dev at famic.de (Martin M.)
Subject: Private repos & auth
Date: Thu, 20 Jun 2019 23:08:26 +0200 [thread overview]
Message-ID: <20190620210826.GA18493@remote.famic.de> (raw)
In-Reply-To: <20190613212052.GB2485@remote.famic.de>
> So, what is the best practice for using private repositories beside
> public one in cgit? Any help is welcome!
After some more tinkering and going back to HTTP Basic Auth, I figured
out a robust and, IMHO, elegant way to solve my requirements. It may not
be the right approach for all because it relies on features of the h2o
web server. But since I recently switched to it anyhow, it fully
integrates in my personal setup (btw, h2o is a fresh breeze after years
of Apache configuration struggling and its performance is outstanding -
you might want to give it a try)
https://github.com/h2o/h2o/wiki/Hosting-private-and-public-repositories-with-cgit-and-Gitolite
prev parent reply other threads:[~2019-06-20 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 21:20 dev
2019-06-20 21:08 ` dev [this message]
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=20190620210826.GA18493@remote.famic.de \
--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).