Web server config files are mostly about expressing HTTP handling logic. Often, various handlers or middlewares need to be “composed” to form a cohesive HTTP handler that returns the desired responses. Structurally, config files are basically limited to two dimensions: rows and columns (or, lines and tokens). Syntactically, a config file’s second dimension can expand into more dimensions or scopes when blocks are opened (which are usually represented by curly braces { } and/or indentation, simi...

Hi @acole, welcome to the Caddy community. Caddy doesn’t have the site enable / disable aliases Apache does that moves/removes symlinks automatically, but Caddy can import multiple files when starting up, just like Apache does. You can use one central Caddyfile with import directives, e.g. import /path/to/site1/Caddyfile import /path/to/site2/Caddyfile # ... rinse and repeat Or just one import directive that fetches a glob: import /path/to/*.caddy Then populate the /path/to/ directory with...

Learn how you can use xcaddy to build custom Caddy binaries with non-standard modules to bring new features to your web server.

In this article you are going to learn how to setup request rate limiting in Caddy using a non standard module.

Caddy 2 Caddyfile usage examples.

Build an Open-Source Web Application Firewall stack with advanced monitoring capabilities using OWASP Coraza.