From: Ian Barton <lists@wilkesley.net>
To: Bastien Guerry <bzg@gnu.org>
Cc: Arun Isaac <arunisaac@systemreboot.net>,
emacs-orgmode@gnu.org, Konstantin Kliakhandler <kosta@slumpy.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Why no secure code retrieval
Date: Sat, 2 Jul 2016 17:51:30 +0100 [thread overview]
Message-ID: <20160702165130.GA1401@scamper2.bantercat.co.uk> (raw)
In-Reply-To: <87lh1k5dj1.fsf@free.fr>
On Sat, Jul 02, 2016 at 04:18:42PM +0200, Bastien Guerry wrote:
> Hi Nicolas,
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
> > GPG signing tags is OK, but I wouldn't like to request every commit to
> > be signed.
>
> Agreed.
>
> >>> I know that https can be a bit tedious to setup so I am not asking for it
> >>> (though I do think it would be great if it was enabled on the site in some
> >>> fashion).
> >>
> >> HTTPS is not so tedious these days with Let's Encrypt.
> >>
> >> https://letsencrypt.org/
> >>
> >> We should set up HTTPS as well.
> >
> I'm considering paying for a digitalocean instance, with https via
> letsencrypt for both the website and git.
>
> I'm also considering switching from our current git setup to using
> Gogs (https://gogs.io): this would ease the process of adding new
> contributors, welcoming more org repositories, etc.
>
> The other solution would simply to use https://savannah.gnu.org.
>
> One remaining problem for both gogs and savannah is to ensure web
> references to commits are correctly redirected, which I think is
> one line of nginx configuration.
>
> I'm curious to know what people think about the switch to something
> like gogs*.
>
> Thanks,
>
> * gitlab seems too heavy, and I'm more experienced in maintaining
> gogs instances than gitlab instances.
>
> --
> Bastien
>
Not heard of Gogs before, although it looks nice. Another possiblity
would be gitolite with cgit. Gitolite is very flexible and as a
consequence can be hard to set up initially. The documentation is very
comprehensive. It supports mirroring of repos.
--
Best wishes,
Ian.
next prev parent reply other threads:[~2016-07-02 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 12:10 Why no secure code retrieval Konstantin Kliakhandler
2016-06-29 6:11 ` Arun Isaac
2016-06-30 11:50 ` Nicolas Goaziou
2016-07-02 14:18 ` Bastien Guerry
2016-07-02 16:51 ` Ian Barton [this message]
2016-07-03 7:09 ` Bastien Guerry
2016-07-03 15:11 ` Robert Klein
2016-07-03 15:20 ` Achim Gratz
2016-07-03 16:57 ` Robert Horn
2016-07-03 18:18 ` Konstantin Kliakhandler
2016-07-03 18:25 ` Achim Gratz
2016-07-03 20:12 ` Robert Horn
2016-07-03 22:36 ` Konstantin Kliakhandler
2016-07-04 0:17 ` Robert Horn
2016-07-04 6:15 ` Konstantin Kliakhandler
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160702165130.GA1401@scamper2.bantercat.co.uk \
--to=lists@wilkesley.net \
--cc=arunisaac@systemreboot.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kosta@slumpy.org \
--cc=mail@nicolasgoaziou.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).