For years I’ve been running my Nextcloud on bare metal. Now I finally decided to switch it to docker. I looked into Nextcloud All-In-One and it seems easy to deploy but it lacks configuration options like multiple domain names and putting it behind a traefik reverse proxy is kind of a pain to set up.
You can check out my solution on GitHub. I decided on a docker compose setup with nginx, php-fpm and redis(redis is now replaced by KeyDB) in separate containers. Obviously it’s for experts but it’s a lot more configurable. than AIO. It’s also just as easy to migrate to as with any bare metal setup and just as configurable.Yes it’s still a pain to set up, but better than the bare metal version lol
What do you guys think about putting the different components (webserver, php, redis, etc.) in separate containers like this, as compared to all in one? Feedback is greatly appreciated!
NextCloud’s
trusted_proxiessetting supports CIDR notation, so it mught be better to set the subnet of Traefik’s network as opposed to the IP address. That way, if you ever need to do anything with the container (I.e. upgrade traefik), the IP can change but the subnet is less likely to change.True. That’s a good improvement. Thanks a lot! By the way do you know if the nextcloud
trusted_proxiessetting allows for hostnames such as “traefik” as compared to just IP addresses?The documentation seems to suggest just IP address and CIDR notation.
Alright, thanks a lot! You probably saved me a lot of headache in the future
No problem! It’s a small change that might not affect most people :)