People usually come here looking for advice on how to replace their dockerized nextcloud setup with a bare-metal setup. Now you came along presenting a solution to do the reverse! Bravo!

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?

I actually has a similar setup, but with nextcloud apache container instead of php-fpm, and in rke2 instead of docker compose.

If you weren't aware, Nextcloud provides non-AIO compose files in their docker repo: https://github.com/nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml

NextCloud’s trusted_proxies setting 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.

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?

It's much better to separate them. You can update them separately, you can configure and fine-tune them separately, you can reuse the images for different apps, you can reuse a container for multiple apps etc.

Not to mention not having to rebuild the all-in-one image yourself, which can get very finicky.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

2 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

[Thread #661 for this sub, first seen 6th Apr 2024, 23:25] [FAQ] [Full list] [Contact] [Source code]

Docker runs on bare metal