Re: Private code: to forge, or not to forge?

On Wed, 2024-10-16 19:24:32 +0200, Daniel Baumann wrote: > On 10/16/24 18:18, Iustin Pop wrote: > > Gitea/Forgejo are common recommended solutions for "home hosting", but > > neither is packaged. > > (jftr) I'm currently working with Forgejo upstream to get one last > feature implemented that we

Re: Private code: to forge, or not to forge?

On 10/16/24 18:18, Iustin Pop wrote: > Gitea/Forgejo are common recommended solutions for "home hosting", but > neither is packaged. (jftr) I'm currently working with Forgejo upstream to get one last feature implemented that we'll need at work to switch to it, and then finish the packaging of it

Private code: to forge, or not to forge?

Hi all, this is offtopic (sorry!), but since we kept discussing Salsa - I wonder, what are people doing for private code? I have around 40 git repositories of private code that I keep, and while a subset of them are somewhat managed (living under a common `gitroot` directory), not all are. Plus, a