Always works great for me.
I just run it (behind haproxy on a separate public host) in docker compose w/ a redis container and a hosted postgres instance.
Automatically upgrade minor versions daily by pulling new images. Manually upgrade major versions by updating the compose file.
Literally never had a problem in 4 years.
I’m still too container stupid to understand the right way to do this. I’m running it in docker under kubernetes and sometimes I don’t update nextcloud for a long time then I do a container update and it’s all fucked because of incompatible php versions of some shit.
I don’t remember much about how to use kubernetes but if you can specify a tag like
nextcloud:28instead ofnextcloud:latestyou should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.There are varying degrees of version specificity available: https://hub.docker.com/_/nextcloud/tags
Make sure you’re periodically evaluating your site with https://scan.nextcloud.com/ and following all of the recommended best practices.
Kubernetetes is crazy complex when comparing to docker-compose. It is built to solve scaling problems us self-hosters don’t have.
First learn a few docker commands, set some environment variables, mount some volumes, publish a port. Then learn docker-compose.
Tutorials are plenty, if those from docker.com still exist they’re likely still sufficient.
Yeah I’m only running it because truenas scale uses it
They have an "all in one" docker installer for the above because you are far from alone here.