And why?
I considered using pijul but everything in Nix/Guix is oriented around git as are the plugins for my text editor and CLI, and there aren’t good self-hosted web frontends that I can use to put pijul projects on my linkedin profile or whatever. I want to switch to it but the ecosystem surrounding it needs to actually exist first.
Thought this was abandoned?
I use sourcehut.
GitLab because for CI/CD is it far, far much user friendly and comfortable to use with GitLab CI compared to GitHub Actions and flows.
In addition I can integrate templates for CI/CD pipelines already defined with the To Be Continuous project (which is open source).
GitLab, because it’s FOSS.
Why not Codeberg, cus its FOSS and run by a donation-funded nonprofit.
You cannot host non-foss code on Codeberg. That’s a possible reason.
Codeberg for all my projects, both private and public. Some are mirrored to Github. Also Codeberg Pages and its Woodpecker CI.
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.
Codeberg. Fully Libre
Codeberg for public repositories, cgit (if that even counts) on my own server for private ones
Gitea because GitHub offers limited features for a free Syrian account
I’ve been selfhosting Gitea for years now and it’s great, but I also don’t really collaborate with anyone else so YMMV. Originally I wanted to go with GitLab utb it’s too resource intensive for my use case
gitea: lightweight, self hostable. preety neat. can also be customized https://git.nowhere.moe
forgejo is a fork made by a nonprofit and deals with security issues much quicker
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).
+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.
I’ve been meaning to switch over from Gitea to Forgejo for ever. I’ll get it done tomorrow ;)
Definitely best to get that done ASAP. Forgejo being a drop-in replacement for Gitea won’t be guaranteed ever since the hard fork:
To continue living by that statement, a decision was made in early 2024 to become a hard fork. By doing so, Forgejo is no longer bound to Gitea, and can forge its own path going forward, allowing maintainers and contributors to reduce tech debt at a much higher pace, and implement changes - whether they’re new features or bug fixes - that would otherwise have a high risk of conflicting with changes made in Gitea.
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.
When you say you host it live on Codeberg, do you mean something akin to GitHub pages? I didn’t know that existed
Oh that’s so cool! Thanks for the link.
Yup, that’s what I mean
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
.GitLab. The CI is fantastic.