Oh wow! Quite a journey!
I’d consider Paperless a hall-of-famer for self-hosted software and something most people who get into self-hosting discover at some point, even if they don’t use it.
So thanks for building it, even if you’ve moved on. You gave the forkers something great to build from.
Legend!
Do you use NGX yourself?
I recently tried out Cockpit on top of plain old Debian and it was really nice. You can manage VMs and whatnot, but it’s quite a bit more lightweight than Proxmox IMO.
But rebuilding a bare metal server properly compatimentized took me a few hours only, so is that really so important?
Depends on how much you value your time.
Compare a few hours on bare metal to a few minutes with containers. Then consider that you also spend extra time on bare metal cleaning up messes. Containers don’t make a mess in the first place.
Add it to your fstab
Well said.
The spirit of Self-Hosting is trying things and then asking specific questions when you get stuck (stuck includes having no luck using a search engine).
It works well for 2-3 services, but as the number of services grew they started to interfere with each other
Can you expand on that? I use docker-compose and have probably around 10 services on the same box. I don’t forsee any limitations beyond hardware if I wanted to just keep adding more, but maybe I’m missing something.
How would you switch regions using a firewall?
I think compose is best used somewhere in between.
I like to have separate compose files for all my service “stacks”. Sometimes that’s a frontend, backend, and database. Other times it’s just a single container.
It’s all about how you want to organize things.
Exactly this, nothing against tools like these, but I’m in it for the learning so I want to get as DIY as possible.
And yeah, it’s super satisfying to see it all come together.
Oooh nice, I’ve been looking for a way to do this!
My solution to this has been to not forward the ports on individual services at all. I put a reverse proxy in front of them, refer to them by container name in the reverse proxy settings, and make sure they’re on the same docker network.