Date: Tue, 04 Feb 2020 10:32:10 -0800 From: "Philip Paeps" <philip@freebsd.org> To: freebsd-git@freebsd.org Subject: Re: Experiences with self-hosted git servers Message-ID: <D999E485-8742-4E1A-945B-47E33F881489@freebsd.org> 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
On 2020-02-04 06:37:57 (-0800), Ed Maste wrote: > 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. One of my customers is using Gitea and ... it's not great. I am not involved with the administration of Gitea but as far as I can tell, it's simply not mature software. It has its own "issue" and "pull request" thing similar to GitHub. Like GitHub it's woefully inadequate for all but the most basic defect-tracking. I don't believe it has neat integrations with things like Bugzilla or Phabricator so we'd have to provide our own. GitLab is a lot more mature and several of my customers have good experiences with it. It has a fairly useable issue-tracking system and a mature mechanism for plugging in external tools such as Buzilla and Phabricator. GitHub also works but it's not clear how well it interacts with external tools. As I understand it, they've also removed their self-hosted solution so I would consider it a non-starter unless there is a way to use it without losing control over authentication (i.e.: I would not trust an external organisation to authenticate FreeBSD developers). Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D999E485-8742-4E1A-945B-47E33F881489>