I’m currently working on a small setup for myself to have my complete home server in a Nix-config. That means, services, backup, etc. And if I can, having everything nice and separated into different files.
Currently, it’s just the few services I need, and a bunch of hard coded constants/passwords, but I wondered if there’s any interest from you guys to use and maybe even collaborate on this kind of project?
Fair enough. I personally think someday someone will have the same niche issue I’ve already tackled and be happy to stumble over my code while googling it. So I just drop most things I do somewhere for other people to find. Regardless.
But concerning NixOS, I also still need to switch over a few things to agenix and generalize parts of my config before publishing it.
I’m still conflicted a bit if maybe the new wiki would be a better place. My Github project is (to a casual googler) just some random bloke on the internet dumping some files, while the wiki is at least somewhat curated and official.
Doing both would be the best, obviously, but I’m also struggling with adulting, so I don’t have that much time on my hands.
Hmm. There is value in both. When I started out with NixOS I read lots of wiki articles. And we all know there is some room for improvement. And I also read several configs of other people to see how things tie together. And to look up things that aren’t documented. Nowadays I just put in what I’m looking for and “language:nix” into Github. So there’s lots of personal configs that turn up. Sometimes with useful stuff. So I think anything is better than nothing. But obviously if you have kids, prefer them and let other people come up with the detailed wiki articles 😆
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Fair enough. I personally think someday someone will have the same niche issue I’ve already tackled and be happy to stumble over my code while googling it. So I just drop most things I do somewhere for other people to find. Regardless.
But concerning NixOS, I also still need to switch over a few things to agenix and generalize parts of my config before publishing it.
I’m still conflicted a bit if maybe the new wiki would be a better place. My Github project is (to a casual googler) just some random bloke on the internet dumping some files, while the wiki is at least somewhat curated and official.
Doing both would be the best, obviously, but I’m also struggling with adulting, so I don’t have that much time on my hands.
Hmm. There is value in both. When I started out with NixOS I read lots of wiki articles. And we all know there is some room for improvement. And I also read several configs of other people to see how things tie together. And to look up things that aren’t documented. Nowadays I just put in what I’m looking for and “language:nix” into Github. So there’s lots of personal configs that turn up. Sometimes with useful stuff. So I think anything is better than nothing. But obviously if you have kids, prefer them and let other people come up with the detailed wiki articles 😆