(no title)
evnix | 7 months ago
I end up just paying a cloud provider and forget about it.
Anyone else on the same boat? What has been your approach?
evnix | 7 months ago
I end up just paying a cloud provider and forget about it.
Anyone else on the same boat? What has been your approach?
SomeoneOnTheWeb|7 months ago
I simply have one folder per service, each folder contains a docker-compose stack and a storage directory. Updating is simply a matter of running `docker compose pull` and `docker compose up -d`. Nothing more.
Breaking updates requiring to tweak the config are very uncommon, and even when they happen it's only a few minutes of checking the updated config and applying it.
IMO this is the simplest way to self-host. No VM, no complex software install, nothing more than a simple Docker Compose setup that's fully automated.
doubled112|7 months ago
If something breaks I can decide to figure out why, or revert.
mirdaki|7 months ago
But also I think using a cloud provider is fine if you're happy with the experience. It is a time sink to get things setup and it's not zero maintenance time. It's reasonable to weight those costs
beala|7 months ago
Joking aside, a minimal setup just using docker compose is pretty manageable. Self hosting many projects is as easy as 'docker compose up -d', and upgrades are straightforward as others have pointed out.