Gitea is not fundamentally different than Forgejo, Forgejo is just a better fork of it. Better in terms of: more contributors, more users, dogfooding (Gitea is built on Github 🤦).

But yes, GitLab is like the Mac of Git forges: everything is included, doing everything their own way, vendor lock, very expensive. There is a community edition but serious users will run into its limitations and it does not integrate neatly with external solutions.

Forgejo is IMO the Linux of Git forges: low on resources, expandable, hackable, stable.

Volsync

Talos is amazing and if you want to start from a fully automated setup (GitOps, Renovate), I highly recommend using https://github.com/onedr0p/cluster-template

Glad you found your ideal selfhosting setup!

Enjoy!

Dococd + renovate goes brrr

It would be nice if you used Lemmy’s builtin “crosspost” feature: that way you can share across communities to reach everyone, but (some) client software we use won’t show it to us 7 times, because it knows it’s the same post.

Now I get this:

Docker Compose is really the easiest way to self-host.

Copy a file, usually provided by the developers of the app you want to run, change some values if instructed by the # comments, run docker compose up and it “just works”.

And I say that as someone who has done everything from distro-provided packages to compiling from source, Nix, podman systemd, and currently running a full-blown multi-node distributed storage Kubernetes cluster at home.

Just use docker compose.

deleted by creator

If you are successful as a content creator, whatever the platform, you have great marketing, communications and branding skills. How transferable do you want the skills to be?

Tell your buddy you can play Helldivers with him!

Helldivers 1 and 2 are platinum and gold rated on ProtonDB with recent reports on both confirming they work well.

https://www.protondb.com/search?q=Helldivers

Had to DDG that, I could only think of (tofu plan)[https://opentofu.org/docs/cli/commands/plan/]

No idea why you’re being downvoted, it looks like an interesting concept:

https://garbagecollected.org/2017/10/24/the-carmack-plan/

If selfhosting the family chat is not a goal in itself and it’s about privacy or being independent from big tech, just take the loss and go to Signal. Much smoother experience than any self-hosted messenger can provide for now.

Yep, as for the last point: the problem was not so much the devs but data going through a Chinese server

If Mint works for you, just stick with it. No need to try a different distribution to compare. You’ll know when you need it.

I would only go to Fedora if you need it. For example newer drivers (kernel, mesa). Don’t go change the kernel and/or mesa on a distribution, probably better to switch at that point. Or if you need KDE or GNOME for some reason. Wayland is disabled in Mint by default, but can be enabled. It’s been over a year IIRC since they added experimental Wayland support so it may be fine by now.

Differences between Linux distributions are exaggerated.

Mint is a great choice, it is very stable, and it really holds your hand via the Software Center.

However, stable also means old: it does not support the latest hardware.

If you have hardware that released after (rough estimate) April 2024, consider something based on Fedora, such as Bazzite, instead. It comes with modern drivers and should support modern hardware much better.

keep it on cache since I do a lot of code compilation, but I will usually switch it to frequency for gaming and stuff.

Isn’t gaming the most cache-heavy CPU workload there is? The X3D CPUs have consistently topped gaming benchmarks, even outperforming much more modern CPUs that lack 3D cache.

I’d sooner do it the other way around: frequency for compiling, rendering, transcoding, etc. Cache for gaming!

The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.

For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues. PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.

Again, 1Gb network is not a big deal, not using PLP drives could cause issues.

If you don’t need volsync and don’t need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.

I tried Longhorn, and ended up concluding that it would not work reliably with Volsync. Volsync (for automatic volume restore on cluster rebuild) is a must for me.

I plan on installing Rook-Ceph. I’m also on 1Gb/s network, so it won’t be fast, but many fellow K8s home opsers are confident it will work.

Rook-ceph does need SSDs with Power Loss Protection (PLP), or it will get extremelly slow (latency). Bandwidth is not as much of an issue. Find some used Samsung PM or SM models, they aren’t expensive.

Longhorn isn’t fussy about consumer SSDs and has its own built-in backup system. It’s not good at ReadWriteMany volumes, but it sounds like you won’t need ReadWriteMany. I suggest you don’t bother with Rook-Ceph yet, as it’s very complex.

Also, join the Home Operations community if you have a Discord account, it’s full of k8s homelabbers.

The article says it can debug TUIs, similar to what the browser’s debug panel does for web apps. That is useful for TUI developers.

Other than that, I don’t know either what Kitty is missing.

Finally, the end of “it doesn’t work on Wayland” is in sight. Just in time for Windows 10 EoL too