ccryx [he/him]

You say you run your containers rootless with systemd quadlets. Are you publishing the containerized apps’ ports to the host and reverse proxying your applications like that or have you somehow managed to attach your (presumably also containerized rootless reverse proxy) and your containers to the same network?

The latter is what I’m struggling with, so currently all my applications are in their own network that the reverse proxy is also connected to. But from what I’ve gathered, that means the proxy and each application need to share a network namespace which apparently isn’t possible in rootless mode unless all applications share the same network namespace.

Thanks, I had a look at both but sadly they don’t seem to support OPDS (or I’m too inpatient).

I found quire which does support opds and has a more modern interface but is vibe coded, not sure how much/what parts of it though.

Unrelated to the topic: what eBook reader with opds support are you using on your phone? So far I’m using koreader which works but is a bit clunky.

All my services run in podman containers managed by systemd (using quadlets). They usually point to the :latest tag and I’ve configured the units to pull on start when there is a new version in my repository. Since I’m using opensuse microos, my server (and thus all services) restart regularly.

For the units that are configured differently, I update the versions in their respective ansible playbooks and redeploy (though I guess I could optimize this a bit, I’ve only scratched the surface of ansible).