On 2024-10-16 21:20:48, Jan-Benedict Glaw wrote: > On Wed, 2024-10-16 19:24:32 +0200, Daniel Baumann <dan...@debian.org> 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'll need at work to switch to it, and then > > finish the packaging of it in Debian. Realistically I expect the > > packages to be ready by end of the year (we have local ones that need > > some polishing/finishing in order to get them acceptable for Debian, as > > well as a bunch of build-depends).. > > That is great news! I am at about the same point as Iustin is. At > work, we're using Gitlab as well (but it's a fat boy.) And > alternatives aren't packaged. So I'll probably be one of your first > users in January (coincidentally, I'll also have three weeks of > holidays!)
I'm also glad to hear! Although, having read more, even the LTS version (of Forgejo) has a very short lifetime, not sure how this will play with Debian releases. Likely keeping sid up with LTS or most recent versions, and relying heavily on backports for stable servers. Daniel, what's your plan? In any case, I've spent the last days playing with Forgejo in a VM, and I'm more and more convinced that the downsides (of having to maintain a forge) are less than the upsides, so I'll probably go ahead with Forgejo from upstream until there are packages. What sold me (after many days of considering the pros and cons) was realising it takes only 5 seconds to create a local mirror of one of my github repos (faster than setting up a cron job to do it, by far), and my surprise at it picking up my github actions config and trying to run the CI - which it failed, sync properly setting up forgejob-runner is more steps. iustin
