Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Feb 2020 08:49:54 -0800
From:      Sean Chittenden <sean@chittenden.org>
To:        Ed Maste <emaste@freebsd.org>
Cc:        freebsd-git@freebsd.org
Subject:   Re: Experiences with self-hosted git servers
Message-ID:  <CAHevUJH5efz4XJv_tq7rfAoeDdRz4KAp0oMqivcjrDC8m8sSgw@mail.gmail.com>
In-Reply-To: <CAPyFy2B0fNg-CiXSi2YjAi-RZ_Y=RrVhBuzEAM4CSnYreoQOyA@mail.gmail.com>
References:  <CAPyFy2B0fNg-CiXSi2YjAi-RZ_Y=RrVhBuzEAM4CSnYreoQOyA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>
> There are a number of options for self-hosting, such as Gitea, GitLab,
> as well as git's plain built-in server. Phabricator (which we use for
> code reviews) also includes a repository hosting module named
> Diffusion.
>

Once upon a time I loaded FreeBSD into gitea to try and float that as a
platform for people who felt strongly about integrated self-hosted SCMs.
It didn't work out well for a repository of our size.  I really, really
want to like gitea, but don't think it's a good fit for this project.  For
other, smaller projects (and let's face it, ~99% of OSS code and corporate
code bases is smaller) gitea works well.  I've used it for a few small
things around the house and am generally pleased (it just doesn't have the
caching and indexing required for large histories).

I am routinely frustrated with developers that select Gitlab for Go and
Rust projects because they have a significantly higher probability of
languishing in a void as undiscovered software, and it normally leads to a
deadend for development because the project can't garner the support needed
to hit critical mass.

I am interested in hearing from FreeBSD users and developers who have
> used one or more of these, or other Git hosting tools - what worked
> well, what didn't? What do you wish you had known before getting
> started?
>

The best solution and one that worked in practice at $JOB-1 was Github.
With the exception of a few unicorn hours, it worked well, was fast, and
required no training to bring in new hires to our project.  We could focus
on the task at hand instead of the services that enabled our productivity
and collaboration.  Credit where credit's due, it's an excellent service
and has also demonstrated an extreme willingness to support our workflow
(including fixing their SVN to git bridge for us, because our repository
was so large).  I like that Github is willing to give us weekly dumps of
our issues and raw PR data, too.

-sc



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHevUJH5efz4XJv_tq7rfAoeDdRz4KAp0oMqivcjrDC8m8sSgw>