Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I've converted everything to NixOS (Desktop, laptop, nas and 3d printer, rpi with home assistant) only my router is still pfSense (and thus BSD). It just makes configuration and updating so much easier from one central configuration. And I don't have to remember what and how I installed something. It's just there in my flake.
I haven't looked at Nix in detail but you got me interested for 3d printers in particular, already have my klipper config in git if an SD card fails on me, going to have to look at doing that for the os too.
I love it for using klipper. But when I started doing it the klipper pkgs did give me some troubles. You can work around them, but know you might find some issues on the way. Maybe it's better now, I haven't really updated that part of my config much recently.
Do know that not all arm devices are equally supported. rpi 3 and 4 are, the rest is community based (see: https://nixos.wiki/wiki/NixOS_on_ARM). Personally I run klipper on a x86_64 thin client for this reason and because raspberry pi's were scarce and expensive back then.
How quick could you pick it up? And how does it handle one config for different devices (due to different hardware(fstab/cryptsetup differences), propietary/non-mainlined drivers?
I have been thinking about switching because I'd love a reproduciable system but fear it would take some of that flexibility I rely on (I've had some issues with ftstab/cryptsetup and initramfs customizations on the fedora atomic base of bazzite on my steamdeck).
Best advice is can give you is to #DOCUMENT everything you do for what reason and how it works inside your config file. So you know what each code block does and how it executes making your entire config dummy proof also helps learn the syntax super fast!
I have to be honest and say it was a journey. Nix in itself isn't really difficult I find. But everything together and finding the right documentation and figure out how NixOS comes together can be a bit daunting.
But a simple straight forward config is pretty doable. My advice is to start small and build up. You can reuse your old dotfiles and include them in the configuration directly, so you don't have to convert everything to nix (right away). Also don't scare away from using flakes, they are the way to go in my opinion.
You can define multiple hosts/systems in one configuration with each their own
nixosSystemcall. So you can define hardware/fs/network etc per system.Also I like to add that the vimjoyer video's on nix helped me with understanding some of the concepts, They are usually short and straight to the point.