Always remember: RAID is not a backup.

Having only one backup and the server dying means you now have no backup, therefore the 3-2-1 scheme for backups is worth looking into.

That depends a lot on what you’re hosting resp. if the mobile apps are using Google’s/Apple’s messaging/notification services.

You can use -f /path/to/compose.yaml to call it from wherever you like.

The official NC docker container uses the “www-data” internally to run the services. This will get important if you ever want to run tasks via “docker compose exec”.

You can use quite a number of “underlying” distributions, it mainly depends on what you like (Arch-based ones, Debian-based ones, etc).

As a desktop environment, have a look at XFCE or LXDE.

What are the main advantages to plex?

AFAIK they offer more apps resp. apps for more platforms. Apart from that, nothing really. Maybe a little more idiot-proof.

Debian as a server base OS is well-tested and (for me) ultra reliably stable.

FreshRSS, + Readably on Android. Has worked well for me for years.

Edited the main post. Seems like there was an issue with “pending” subscriptions. Maybe in combination with being on 0.17.4

Overall it was fine, took a moment to find the proper Traefik settings, but after that it ran basically fine. It’s just too “unstable” for me at the moment from a development standpoint, moving too rapidly. Maybe I’ll do another one once it has matured and slowed down a bit.

That would have been plan C, yes. But it’s not a proper solution, it’s a hacky workaround which puts unneccessary load on the federating instances.

I did. Unsubscribed, then purged from the local DB. I’ll work through the logs, see what the other instances are trying to push.

Yeah, 0.18 seems to have introduced a number of new and exciting bugs.

everyone

Now that’s what I’d call a stretch…