And why?
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. 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.
- the cool kids use Sourcehut
- I use Codeberg
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).
holy shit man
I’m not cool enough to use Sourcehut and deal with patches and emails - they’re already a pain in the ass when I submit patches to GNU, so I stick to Codeberg.
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 for public repositories, cgit (if that even counts) on my own server for private ones
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
GitLab, because it’s FOSS.
For Darcs I have been using darcs hub & mirroring to my server. That said Smederee has slowly but surely been shaping up to be a better replacement (recently got reStructureText support!); once they have
obliteratesupport, I will be tempted to make it primary for real since it covers all the basics.For Pijul, I can really only use it self-hosted over SSH. Nest is far too feature barren to be usable—especially without the ability to fetch tarballs for instance where you can’t have or use the
pijulbinary for fetching (which is a bit ironic since the Pijul binary has anarchiveto create tarballs, Nest just doesn’t expose it). Pijul is faster & the key concept of separating your commit ID from details (such as Darcs or Git usingName <e@mail.address>as the identifier) is much nicer not just for privacy if wanted but changing these details for whatever your reasons maybe (imagine changing your name after marriage or sex change & trying to convince all projects you’ve committed to to rewrite their history with your new info to not be confused or dead-named—most maintainers would ignore you). Someone should write a decent, lightweight forge so Pijul can be usable.I use Darcs/Pijul since Patch Theory is a better model than snapshot-based version control as seen in Git/Mercurial & others. Since neither have many hosting or forge options, there are not many choices (answering the “why?”).
If using Git, an inferior VCS IMO, things are now going hosted on Codeberg. In the past, I had paid for SourceHut & while it was a generally nice, lightweight experience I was disappointed with the features & progress to the point I didn’t feel I was getting good value (also no Darcs or Pijul support, just Git & Mercurial). Since I don’t write any of my own code using Git anymore, I don’t really bother self-hosting cgit, Ayllu, or something. That said, Forgejo is a pretty disappointing in its direction as they choose to clone more features from MS GitHub than even Gitea which basically leaves you with MS GitHub but FOSS without addressing some core issues (PR workflow is not good, YAML-based CI is not good, & so on); a better sell IMO would be fundamental improvements on these old models/workflows that would inspire leaving for technical reasons instead of social/political/philosophical reasons.
As much as I hate GitHub, for in-person projects involving multiple people I usually end up having no choice since they usually think GitHub is the most important programming tool ever and nothing I do is going to convince them to create an account on something that’s not GitHub.
For personal stuff I use Forgejo and disable everything except the code view, so I have a quick way to show people stuff I’m doing (for career reasons).
If I was doing a project with multiple people and actually got to chose the platform I would probably use Forgejo or Codeberg and make use of the project management features.
Pijul looks interesting but the ecosystem is very lacking and it doesn’t integrate well with Guix which I base a lot of my workflows around, so until this improves switching to pijul creates more problems than it fixes. The only other VCS and frontend I’m familiar with is GitLab which I don’t use anymore self-hosted since Forgejo is more performant and the main version randomly deleted all my repos and changed all sorts of stuff.
cgit also looks interesting, I might look into it.
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
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.
This is actually why I prefer using pijul. I don’t want to commit my secrets to a git repo and nix will refuse to build because I’m pulling in files that aren’t tracked. Simple solution is to not make the flake directory a git repo and it won’t complain. That’s my solution at least. I also prefer using git (and therefore pijul) via cli rather than as a text editor integration so my experience differs.
I use git primarily via cli also, the text editor integration (with helix) highlights information such as what lines haven’t been committed and makes it easier to access other files in the repo, the fish integration tells me if there’s files that haven’t been committed or commits that haven’t been pushed without having to run git status
I do use helix but haven’t taken advantage of the git integration. Maybe I’m unaware of its power. For fish, I defined my own fish_prompt function with an indicator if there are uncommitted changes. It’s just running
git statusunder the hood. I have a TODO in that function to run apijul diffin the directory ifgit statusreturns nothing…
Do you really use it or are you just adding an alternative to the conversation? It is an interesting concept (commutation) but not likely to supplant git.
I use it for self hosting because all I need installed is sshd and the pijul package. Then I can set my server’s ;p as my remote. The “nest” web UI (the Pijul equvivalent to git tea) is in development and not open source yet, but you can use the hosted version at https://nest.pijul.com/ if you’re curious.
Thought this was abandoned?
The 1.0 is in beta. There has been a lot of refactoring to get it to this point. I would say there’s still many quality-of-life features missing that would stop me from using it in a professional setting but for hobby projects it’s meeting my needs (and gets better with each new beta build). They only have a few project backers but the main developer has been working very steadily on it.
Gitea because GitHub offers limited features for a free Syrian account
