I get that, I plan to add another pihole ad some point so I can enter 2 nameservers at my router. There are solutions to sync all config between the piholes.

Semi monthly sounds like “monthly, or not” to me. Not sure about the alternatives I’ve seen so far

Cool, thanks!

I also planned to do the same (bare nginx instead of NPM but otherwise the same). Did you just remove the nginx container from docker compose and use the same arguments in NPM or do you double-reverseproxy or something else?

I mean every other week. I wasn’t aware of the other interpretation, but I think in combination with “The Sunday thread” it’s unambiguous?

I have never heard fortnightly, but then I’m not a native speaker. Is that commonly used?

I would run Debian from a stick and install Proxmox with the installer and not on top of Debian unless you have to. While the latter works, I found some settings around network interfaces to differ between the installation methods which caused me problems here and there.

Did you check Mint recently? If it’s been a while, it could also be dust buildup at the fan.

If you want to have domains assigned to local IP addresses, you can also use Pihole as a local DNS! It’s a very nice tool for adblocking on network level anyways, can only recommend it.

Cool! Which installation method did you use?

I hadn’t heard of Talos Linux, sounds cool! We are using haproxy as ingress controller with stepca for local certificates at work.

I didn’t know that, cool! Though I should probably talk to the mods before setting up such a thing.

Personally I’m mostly involved with my homelab migration so there’s not too much on the selfhosting page except os updates. I set up meshmini earlier to access my thin clients via vPro/AMT but I need to configure the clients before being able to actually using meshmini. Once I’m done with that I’ll finally be able to set up Lemmy and Pine pods.

My selfhosted stuff currently works fine without me doing much which feels good and lets me focus on hardware stuff currently.

Not answering every single point but generally: I’d set up proxmox, test everything, make notes, reach a state/config that you like, and then start over doing it “properly” from start.

Personally: ZFS yes, quemu/lxc depends on use case

I shy away from running all services as Docker on the same machine for backup/restore purposes and rather have VMs per service. Is there anything wrong with this approach?

No, but you’ll have much more overhead. I have a VM that hosts all Docker deployments which don’t need much disk space (most of them)

Personally I’m waiting for Ghost to support Activitypub but generally exposing WordPress is perfectly fine.

Use whatever you have and test different setups. I would start by installing Proxmox and setup ZFS on some drive that not the boot partition. For just checking it out with some lightweight VMs and containers any CPU that’s not 20 years old will suffice, the more RAM the better. Play with VMs, backups etc in small scale. You can use your old external USB HDD, etc, just to figure out things like ZFS.

Don’t buy anything before getting some experience and having some kind of plan.

Hm, I never really liked Conversations and decided to end xmpp for good. Maybe I need to give it another try but I really like some Matrix features.

Better mobile clients? Have things changed this much in the least three years?

It’s easy to oversee because of the generic name, but this is pretty much that: https://hub.docker.com/_/registry

Edit: forgot there’s jfrog artifactory as well

I can’t say much to docker in LXC as I’m not using it, I vaguely remember some limitation I’ve read of but if it works fine for you those don’t seem to apply.

A VM has more overhead than an LXC, but with several LXCs maybe a single VM wins on overhead.

I currently have most Docker containers in one VM and am thinking about splitting it, the main reason is that 2 deployments have way larger volumes than the rest. This leads to the snapshots of the VM being very large as well and if I would need to restore from snapshots for a “small” application, it would take super long because of the large ones.

A single VM may be a bit easier on maintenance than several LXCs.

If you don’t have a specific reason to switch, I would not.

Moodle can also use collabora.