It sounds like you’ve found your ideal distro. Great! Not everyone will have the same exact use case for their Pi’s.
I’m just a little disgruntled because I like treating my Pi’s as headless servers, often with a single purpose, and I don’t want to have to erase the SD cards to upgrade versions.
Absolutely! I have used multiple origins for posting my projects to Gitea/Forgejo and GitHub. You can also mirror repositories from one site to another, too, although it requires a clean slate for pulling from another remote.
The biggest use case for me is documenting (as code) my home network setup on my private forge.
You may or may not be a developer, but I would like to vote for Gitea/Forgejo. Should you ever get a grasp of git, a git forge is great for keeping code and even plain text documents recorded. It’s my favorite self-hosted service by far.
It can even operate as an OIDC server, so you can create a single login for all your services (that support OIDC).
I’ll also recommend Grist, an alternative to Google Sheets (and Notion, I believe?). It’s a web interface to spreadsheets that supports Python code as formulas. (I’ve also tried Nocodb, another Notion alternative, and I much prefer Grist.)
That’s very fair. Everyone has a different use for Pi’s, and I just happen to favor long-lived devices that can be updated easily. I wish more of the pi internals were upstreamed too.
The devs have started releasing 64-bit builds since then, yes. However, they still push people to the 32-bit builds: https://www.raspberrypi.com/software/operating-systems/
I understand their thinking. They want a unified build experience, to simplify their development and user experience.
I believe you may have found your ideal OS. Debian will always lag behind ever so often. And that’s okay. We all use the Pi’s for different reasons.
This is probably a hot take, but:
I disagree. The OS doesn’t run a mainline kernel, and the Raspberry Pi devs recommend a clean slate on OS upgrades. Granted, they do some trickery for performance with their Zero (not 2) line, using armhf instead of the slower armel, but this doesn’t excuse the fact that Raspberry Pi OS is so brittle. The builds are also still on 32-bit, even though every Pi since 3B can run 64-bit OSes.
I just run Debian on mine. Can’t be assed to clean flash my devices each major update.
I’m not from the UK (or the Commonwealth) but I had some of these books as a child. Loved them. Thanks for posting this.
Incredible yet accurate analogy
If you’re using git to version Caddy configuration, you can use a pre-commit hook to test it, ensuring that you’ll never have invalid configuration. That’s what I do.
caddy validate
There’s some extra command args that may be necessary but that should be an adequate first step.
Epic divested itself of Bandcamp last year. I’ll continue supporting artists that way
I haven’t looked much into the differences, but from my brief research, it appears that Forgejo has just recently updated such that migration from Gitea is no longer possible. I knew that they had become a “hard” fork last year but it has now diverged.
From a feature standpoint, I know that Forgejo is working on Fediverse integration. Beyond that, I think the differences are less apparent.
So to answer your question, I use Gitea and have for a long time. They’ll still remain MIT-licensed even if it’s no longer fully open source. However, the owning company can (and may) cease open source development. If I had known of Forgejo breaking away earlier, or if I were a new user, I would have probably started with Forgejo. That’s my recommendation.