It should support automatically generating a LetsEncrypt for the generated Azure domain name. This is the current part of the docker-compose.yml that pertains to Caddy that would need to be updated as well.
command: -default-sni HOST_IP -conf /etc/Caddyfile
Thanks matt for your warmth welcoming, I’m great to be part of this community, and I would like to learn more about caddy, maybe this is the best opportunity that I have… I have gone through the guide, but I would like someone to take a look about my conversion of caddyfile v1 to v2 and tell me what am doing wrong.
There is no file_server subdirective for reverse_proxy, and you can’t chain subdirectives on one line in this manner. The equivalent in your v1 Caddyfile is to except those paths, but that’s not actually how its done and it’s not even necessary at all, as far as I know.