szaimen / aio-caddy Goto Github PK

If you have stalwart mail in the stack, the first time you stop docker service (or reboot the box) the detection just goes fine. But when you do for the second time, caddy keeps restarting.
I've found a solution, changing the detection of stalwart in start.sh
I've changed line 53
if [ -n "$(dig A +short nextcloud-aio-stalwart)" ] && ! grep -q "mail.$NC_DOMAIN" /Caddyfile; then
by
if [ -n "$(dig A +short nextcloud-aio-stalwart)" ] && ! grep -q "mail.{$NC_DOMAIN}" /Caddyfile; then

As the Caddyfile is in the container, everytime it is updated any added services would be overwritten.

Please have the Caddyfile created in /data i.e. nextcloud-aio-caddy

https://github.com/nextcloud/all-in-one/blob/ecb0ba780dceb684347ecd2757ff74a4be9e94d7/Containers/apache/start.sh#L24

Im not 100% sure, but I think there is missing directive in file start.sh

reverse_proxy nextcloud-aio-stalwart:8080

There is a new port number for web admin interface from version Stalwart mail 0.7.

Always update the container when a new alpine version was merged

See https://github.com/szaimen/aio-caddy/blob/main/Dockerfile

See #7

If we have something else running on our server besides AIO, it might be interesting to allow the aio-caddy container to import rules from users. Perhaps we could mount a volume pointing to the local $PWD/caddy directory where users can add some Caddy files, and then the start.sh script can import them into the Caddyfile.

I'm new to Caddy, but I think this is something that's possible.

I just want your opinion before making any PR. This could allow users to easily set up Caddy with automatic reverse proxies for other community containers without needing to set up a reverse proxy for Nextcloud AIO just to add other rules.