4 ms·
Right, but the parent comment seemed to imply that the same was true for caddy. I was asking what caddys language runtime was (besides via plugins like frankenp
by SahAssar 2y ago
Right, but the parent comment seemed to imply that the same was true for caddy. I was asking what caddys language runtime was (besides via plugins like frankenphp)?
- chuckadams 2y agoPlugins would be it, so you could say Go is Caddy's runtime. Which is of course duh, but since the official mechanism to extend it is by statically compiling in go code, it's also accurate. It's not like nginx and apache are that much different, their "language runtimes" also boil down either to extensions linked into the server or proxying to a backend through another protocol like FastCGI. Caddy supports fcgi out of the box, even using PHP's default settings with one line of config, but I'm not a big fan of php-fpm, and I like having just one daemon to supervise.
- SahAssar 2y agoSo walking back to the comment (https://news.ycombinator.com/item?id=40543839 https://news.ycombinator.com/item?id=40543839) this started at: > It’s pretty much like Caddy vs. nginx: Language runtime, static asset serving, TLS, routing and so on bundled in a single package. That makes it very easy to deploy a container, for example. > Using unit or caddy, you can simplify this to a single container that achieves it all, easily. With caddy this is not true, unless you have compiled in your own plugin (custom or frankenphp), right? All I was asking is what they thought the language runtime for caddy was.