After COVID, I forget common words in the middle of speaking now which has been fucking fantastic in work environments.

“Hey can you hand me that…um…uh….that piece of paper for coffee grounds?”

“A filter?”

“Yeah that”

No, you actually caught be at the perfect time, the transfer to my temporary pool is almost done. I was just curious how inheritance worked on a pool but after giving it some thought, your recommendation makes more sense; turn it on when I know I need it vs turn it off when I know I don’t. Thanks for the advice.

Let’s say I did turn on compression on root. I can’t then turn it off on a per file system basis where it isn’t needed?

Yeah I’m not excited about the write and rebuild times being slower but the read times should still be pretty good. Considering I don’t have any more space for drives in my server and I don’t know how crazy hdd drive prices will get in the next 12 months, the guaranteed 2 drive failure resiliency is more important to me at the moment. My current 1 drive failure resiliency, 2 if I’m lucky, has me worried. My backups are on shucked drives and I don’t want to be put in a situation where I have to rely on them to restore 😅

Thank you for this

I’ll look into it, thanks.

I’m still in the information gathering phase. Do you know if the element client works with the continuwuity server? Is it as easy as entering the domain, user, and password in the client?

Fair criticism. I just don’t have a lot of free time. I can invest in Element but I wanted to crowd source information to see if it was worth it or if there was an easier way. It doesn’t get much easier than Docker

Out of curiosity, what makes it better?

A quick search says it’s a package manger for kubernetes. Besides plex, everything I selfhost is just for me. Would you say helm/kubernetes is worth looking into for a hobbyist who doesn’t work in the tech field?

Linux has gotten really good over the last ~15 years. It used to be that if you didn’t have the most up to date packages, you would be missing game changing features. Now, the distribution you use almost doesn’t matter because even the older packages are good enough for most things.

To answer your question, if it weren’t for gaming, no I wouldn’t mind using Debian as my daily driver. If I ever needed a new package for whatever reason, I would use flatpaks, snaps, docker, or Distrobox to get it.

Personally, yeah it’s the old packages. I want to play games on my desktop and have the newest DE features. An arch based distro seems like it’ll keep up better than Debian.

For my servers though, I only use Debian.

I’m assuming you mean LXC? It’s doable but without some sort of orchestration tools like Nix or Ansible, I imagine on-going maintenance or migrations would be kind of a headache.

You might come across docker run commands in tutorials. Ignore those. Just focus on learning docker compose. With docker compose, the run command just goes into a yaml file so it’s easier to read and understand what’s going on. Don’t forget to add your user to the docker group so you aren’t having to type sudo for every command.

Commands you’ll use often:

docker compose up - runs container

docker compose up -d - runs container in headless mode

docker compose down - shuts down container

docker compose pull - pulls new images

docker image list - lists all images

docker ps - lists running containers

docker image prune -a - deletes images not being used by containers to free up space

he is still completely new to this so I want things to work out perfectly for his first experience.

Of the two options you gave, I’d go with Mint. If your friend runs into a problem, it would probably be easier to diagnose the issue since it’s just Ubuntu/Debian under the hood.

Once they get used to it, they can try other gaming specific distros if they want to try to get a little more performance.

Should I just learn how to use Docker?

Yes. I put off learning it for so long and now can’t imagine self-hosting anything without it. I think all you have to do is set a static IP to the NIC from your router and then specify the IP and port in a docker-compose.yml file:

Ex: IP-address:external-port:container-port

services:
    app-name:
        ports
            - 192.168.1.42:3000:3000