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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
Yes. Everything is NixOS. Because it's perfect for everything.
And it's very handy for this, I have the same config for all my devices (desktop, laptop and server). Enabling and disabling different modules depending on the host it's deployed to.
Yep, exactly.
To be fair, if you use Debian, Arch, Fedora,... long enough, you also know how to tweak your machine for every purpose. In Nix, it's just somewhat of a self-fulfilling prophecy, because you have to know how to tweak your system to achieve.... anything, and then it's the same tweaking mechanics for every other purpose as well.
What is the learning/on-boarding curve for this?
I ask because my home folder has a giant just file I use to script everything. I feel like Iโm 80% there to just migrating.
It's a very steep curve to start, with some additional minor steep parts along the way, but it's not a long curve. Once you got the core concepts and the basic language constructs, you've learned most of what you'll ever need.
Two nice resources: search.nixos.org is super handy, and you can search GitHub with language:nix and a search term to get tons of examples from other people.
Oh, and nix and just is actually a pretty common combo!
Nice, I'll have to remember that GitHub trick. The main thing I've found lacking so far is config examples.
I'd say that if you're an experienced developer, the learning curve is probably overstated, at least based on my limited experience. I'm still a relatively new user, but I'm feeling pretty comfortable with it so far.
Hitting obscure issues with limited documentation and barely any forum discussions on it in search results is killing me though. But at the same time NixOS makes a lot of things incredibly easy and offloads having to remember any changes so it's worth all the effort for me.
Same here, except the steam deck.
My Steam Deck also runs NixOS.
Because this way I can much more comfortably configure it, plus everything game related I automated through nix for my Desktop (e.g. mod installs, reShade config,...) immediately and without any extra steps also applies to the Steam Deck.
https://github.com/Jovian-Experiments/Jovian-NixOS