|
|
|
|
|
by 0xbadcafebee
1339 days ago
|
|
So it's mod_php for Caddy, in reverse? The traditional idea is to build a plug-in for the parent webserver. By essentially "making a fork" of Caddy, if you want to add other plugins to Caddy and then incorporate them into FrankenPHP, it's a lot more work. If instead you ship a PHP plugin to Caddy, you can manage Caddy instead and mix and match different functionality in one place. But I guess it's heretical to suggest somebody use plugins in Go, if the whole idea is everything is a static binary. |
|
It uses mainline Caddy: https://github.com/dunglas/frankenphp/blob/main/caddy/go.mod