4 ms·
Caddy is good, especially for super simple static sites. As soon as it gets somewhat complex, the configs start becoming messy and opaque, eg. Nginx: rewr
by sam_goody 2y ago
Caddy is good, especially for super simple static sites. As soon as it gets somewhat complex, the configs start becoming messy and opaque, eg.
Nginx:
rewrite ^/old/((\w|-)+) /new/$1.php;
Caddy:
@oldPath {
path_regexp old ^/old/([\w-]+)
}
rewrite @oldPath /new/{re.old.1}.php
And many things are not even handled by Caddy, or fail silently (for example, we could not get NetData to reverse_proxy behind Caddy no matter what we tried, and the logs were completely useless.)
- francislavoie 2y agoYou can shorten it: @oldPath path_regexp ^/old/([\w-]+) rewrite @oldPath /new/{re.oldPath.1}.php Having matching and handling be separate steps are a huge benefit to composability of config, you can have pluggable matchers and handlers. Re you issue with netdata, ask on the forums for help.