<div dir="ltr"><div>Just that popped up in hackaday site.</div><div><br></div><div><a href="https://hackaday.com/2018/06/27/keep-it-close-a-private-git-server-crash-course/">https://hackaday.com/2018/06/27/keep-it-close-a-private-git-server-crash-course/</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 8, 2018 at 7:33 AM, Solomon Peachy via Ale <span dir="ltr"><<a href="mailto:ale@ale.org" target="_blank">ale@ale.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Jun 07, 2018 at 11:08:41PM -0400, Steve Litt via Ale wrote:<br>
> Did you set it up in your house or office, or on a remote commercial<br>
> ISP via VM or shared? I'd like to do this, but I have absolutely no<br>
> confidence in my security abilities.<br>
<br>
</span>I have my nearly 5GB instance running natively on the same Fedora-based <br>
shell server that hosts the entirety of my online presence. It's <br>
sitting in a closet at home, with Comcast Business providing the pipe, <br>
RAID1 storage, nightly backups, and a UPS keeping FPL's worst tendencies <br>
at bay.<br>
<br>
I've previously hosted gitolite instances on $5/mo VPS hosts too; it's <br>
fairly light with respect to resource usage.<br>
<span class=""><br>
> Would you say that gitolite is, inherantly, more secure or less secure<br>
> than providing read-only access via git's provided server, and write<br>
> via ssh keys requiring passwords?<br>
<br>
</span>That's basically how gitolite works, although you can overlay much finer <br>
grain control than raw ssh access would otherwise allow. The gitolite <br>
instructions are comprehansive, and should be able to get you to <br>
whatever configuration you want.<br>
<br>
The way I have it configured, access to private repos, and write access <br>
to any repo, requires use of git-via-ssh, which in turn requires an ssh <br>
keypair. That said, most of what I have hosted is public, with the <br>
standard 'git' daemon and cgit given permission (via gitolite) to expose <br>
read-only access without any authentication.<br>
<br>
Private repos are either for my personal use (eg I have a repo that <br>
consists entirely of documentation supplied to me under NDA, and another <br>
that hosts my gpg-encrypted password database) or for working trees for <br>
my commercial clients.<br>
<br>
I can go into more detail (and post snippets of my configuration) if <br>
you'd like.<br>
<br>
I keep meaning to set up something fancier or more integrated (eg <br>
gitlab, gogs, or pagure) but I can't justify it for my own needs. BTW, <br>
I have plenty of resources here and can easlily host more stuff, but I <br>
can't claim to be any more inherently trustworthy/reputable than the <br>
likes of gitlab/whatever... and then there's the problem of Southern <br>
Florida's attractiveness to hurricanes.<br>
<div class="HOEnZb"><div class="h5"><br>
- Solomon<br>
-- <br>
Solomon Peachy pizza at shaftnet dot org<br>
Coconut Creek, FL ^^ (email/xmpp) ^^<br>
Quidquid latine dictum sit, altum videtur.<br>
</div></div><br>______________________________<wbr>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">https://mail.ale.org/mailman/<wbr>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo</a><br>
<br></blockquote></div><br></div>