Configuration is much easier, e.g. this is the full config you need to expose nextcloud on nextcloud.example.com (assuming caddy can reach nextcloud using the hostname nextcloud)
nextcloud.example.com {
reverse_proxy nextcloud
}
Comparing that to ngnix configs that need a template for each different service (although to be fair they’re mostly the same).
Configuration is much easier, e.g. this is the full config you need to expose nextcloud on
nextcloud.example.com(assuming caddy can reach nextcloud using the hostnamenextcloud)nextcloud.example.com { reverse_proxy nextcloud }Comparing that to ngnix configs that need a template for each different service (although to be fair they’re mostly the same).