Forgejo, a Gitea fork used by Codeberg. I chose it because it’s got the right balance of features to weight for my small use case, it has FOSS spirit, and it’s got a lovely package maintainer for FreeBSD that makes deployment and maintenance easy peasy (thanks Stefan <3).
I’ve been meaning to switch over from Gitea to Forgejo for ever. I’ll get it done tomorrow ;)
+1 for Forgejo. I started on Gogs, then gathered that there had been some drama with that and Gitea. Forgejo is FOSS, simple to get going, and comfortable to use if you’re coming from GitHub. It’s actively maintained, and communication with the project is great.
Codeberg. Fully Libre
Codeberg. I host my web portfolio live there and even did a small contribution to kbin when it was alive. It’s great though now I’d want to look at forgejo.
Codeberg for all my projects, both private and public. Some are mirrored to Github. Also Codeberg Pages and its Woodpecker CI.
Woodpecker CI.
Fucking YAML. Nope.
Gitlab at work, because, well, it’s there and it works just fine.
Forgejo at home, because it’s far less resource hungry.
In the end Git is a) a command line tool for b) distributed working, so it really doesn’t matter much which central web service you put in place, you can always get your local copy via
git clone REPO.- the cool kids use Sourcehut
- I use Codeberg
I use sourcehut.
GitLab, because it’s FOSS.
GitLab. The CI is fantastic.
I use Gitlab, but i’m becoming increasingly more unhappy with it over time.
When i have enough resources run another local machine, im planning to switch to switch to Codeberg, with selfhosted Woodpecker CI instead
deleted by creator
self-hosted gitlab.
I love it. I can clone external repos on a schedule and build my projects based on my local cache. I’m even running some automation tasks like image deployments out of it too.
I can clone external repos on a schedule
Some cron deal?
pipeline schedules. once a month I clone the remote repo into a local branch, and push it back to my repo with an automatic merge request assigned to me. review & merge kicks off build pipeline.
I also use pipeline schedules to do my own ddns to route 53 using terraform. runs once every 15 minutes.
also once a week I’ve got about 50 container images I cache locally that I build my own images from.
pipeline schedules
Ah. Cron but from inside the garden. Okay.
No need to talk about containers. Having worked security (and build/rel) they present no net value.
cool.
Gitlab.com and Gitlab ce self hosted
Open source and I’m very very familiar with how ci/cd operates.
Codeberg for public repositories, cgit (if that even counts) on my own server for private ones
sourcehut. I like how it’s structured, where issue trackers, repos, and so on are independent of each other but can be grouped using a project, and you can have as many of each as you want or none at all. You should be able to have a huge monorepo with many issue trackers, or a single issue tracker for a project split across many repos if you want. GitHub doesn’t really allow you to do either, certainly not the former, and same with most of the alternatives. Everything else seems to clone GitHub’s workflow for contributions as well which I can’t stand (sourcehut uses git send-email as the primary contribution method — but there is also a GitHub style PR button —, which apart from the email jank I find much better because once it’s set up you can just send changes to any project with just a local clone; it also means you don’t even have to be registered on sourcehut to send changes to a project hosted there).
I also self-host cgit I suppose but that’s not really a GitHub alternative.
