>I'm a longtime Windows developer who doesn't have much patience with nerdy complexities.
That is funny because I have setup Apache, Nginx, and IIS web servers before and by far the one I found to have the most nerdy complexities is IIS.
That is funny because I have setup Apache, Nginx, and IIS web servers before and by far the one I found to have the most nerdy complexities is IIS.
All in all, I do like Caddy's defaults and out of the box for newer tech. I haven't really tried it much, mostly out of complacency with nginx/iis in Linux/windows. And I will definitely never run Apache on a new box again.
Getting back to Caddy, configuration is so simple, a GUI would be overkill.
Here's an (entire) example of how to configure a reverse proxy in Caddy...
proxy / 127.0.0.1:8080 {
except /favicon.ico /robots.txt /assets /plainpages /staticstuff /test1
proxy_header X-Forwarded-Proto {scheme}
}
The "except" line is a list of files and directories that are statically served by Caddy.All other content comes from a local server on port 8080.
The "proxy_header" line lets the 2nd server know when contents are being sent as secured (HTTPS)
Isn't that nice? I think so.
proxy / 127.0.0.1:8080 {
except /favicon.ico /robots.txt /assets /plainpages /staticstuff /test1
transparent
}
0. https://caddyserver.com/docs/proxy