Support Caddy web server

[Habetdin]

I've tried Automad with the Caddy web server and was surprised that the server was treated as rewrite-incapable.

In fact, even this small Caddyfile is enough to run Automad:

example.org {
	root * /path/to/automad

	php_fastcgi unix//run/php/php-fpm.sock

	file_server
}

... but you'll have to patch the automad/src/server/Core/Config.php:

diff --git a/automad/src/server/Core/Config.php b/automad/src/server/Core/Config.php
index b3efd61f2..f6fd68b04 100644
--- a/automad/src/server/Core/Config.php
+++ b/automad/src/server/Core/Config.php
@@ -304,8 +304,9 @@ class Config {
                $hasPrettyUrls = (
                        (strpos($serverSoftware, 'apache') !== false && $htaccess) ||
                        (strpos($serverSoftware, 'litespeed') !== false && $htaccess) ||
                        strpos($serverSoftware, 'nginx') !== false ||
+                       strpos($serverSoftware, 'caddy') !== false ||
                        php_sapi_name() === 'cli-server'
                );

                return $hasPrettyUrls ? '' : '/index.php';

Alternatively, you can spoof the server on the Caddy side:

example.org {
	root * /path/to/automad

	php_fastcgi unix//run/php/php-fpm.sock {
		env SERVER_SOFTWARE nginx
	}

	file_server
}

I hope that 1-line patch can be added to the Automad v2 because it works great with Caddy :)

[marcantondahmen]

You can set the AM_INDEX setting to an empty string inside the config/config.php. This will enforce pretty urls regardless of the server. At least for now and until Caddy is officially supported.

Please understand that adding support for a web server is not just patching a core file. It also means continuously testing it. The matrix of supported OS/web server/PHP versions is already quite complex and requires a lot of effort on the maintainer's side.

However, I think, supporting Caddy is generally a good idea and hopefully there will be time to do so soon.