First time I have to use it, the spelling really confused me. Wrote unmount and didn’t understand why it didn’t work.

NixOS is a declarative OS. Instead of installing a software, you specify it in a config (.nix file) and rebuild. Same goes mounts, services etc.

I use it because it is great to be able to revert if I do something stupid.

Same here. I remember playing minecraft and wanted to install some mod on my server. There were instructions and I followed them. Problems? Search the web.

I also tried to run TeamSpeak on an RPI at some point, and that was when I learned about ARM.

You are welcome.

I used to support a few companies hosting their own email servers (I supported the mail server software). I will never host my own email, not unless I have a gateway between me and world, someone to configure the DNS and all that.

1. Figure out what you want to host.
2. Read up on what is required to host that.
3. Understand what is required to host that.
4. Skip step 3, wing it and search the internet as you go.

I second Debian because of the amount of information out there.

Since multiple people will be using the same IP when using a VPN. If one person is a bad actor and causes the IP to be blacklisted, it will affect you too.

I recently installed NixOS on my server instead of Debian. OP most have done some really fancy stuff to have had the problems described, but I agree with having to relearn everything from scratch. As for flakes and home manager, I just ignored them. Too much to learn as is.

Use mcfly and it will be even better.

Here is two enteries from my Caddyfile:

ip.domain.tld:80 {
        respond "{client_ip}" 200
}


git.domain.tld {
        reverse_proxy forgejo:3000
}

This is all I need and Caddy will handle the rest. I have created a network with podman/docker that I add to any container that I need to reverse proxy to.

I meant more figuratively. Finally managed to move my compose files to nix files thanks to compose2nix. One thing that throw me for a loop was that podman (or perhaps nix) creates a service named <backend>-<service>. Compose2nix handles this accordingly but I had a few hours of head scratching until I figured that out.

That was an interesting and enlightening read. Thanks!

From all the hate you see, it does look like that. It is not?

I mean keep using port 22 on the server and redirect whatever port you want in your firewall (your router unless you have a dedicted fw) to port 22. Don’t change the ssh port on the server at all.

Why change the SSH port of a home server, which most likely is not reachable from the outside anyway?

And if it is, why change it on the server and not in the fw?

I installed a new server at home and went with NixOS. It looks super cool but it takes so much time to learn everything. The only thing keeping me from going back to Debian is how easy it was to permanently mount drives (and save a configuration for any future install or mishaps).

(I.e. mount, nixos-generate-config, nixos-rebuild switch and done!)

This is spot on!

EDIT: This was spot on. TL;DR below.

I stopped reading after the third word, I’m here for memes, not to read a damned book!

If you trust them enough to use their binary, why don’t you trust them enough to run their install scripts as well?