4 ms·
>the basics of getting it into a package manager should not even be a discussion. Last time I looked into it, their problem was that Caddy plugins must be conf
by bauerd 9y ago
>the basics of getting it into a package manager should not even be a discussion.
Last time I looked into it, their problem was that Caddy plugins must be configured at compile-time, because runtime plugins seem to be hard to do with Golang (besides RPC). Because there's a handful of Caddy plugins, they'd either have to provide a slim package with no plugins, or ship with all or only some blessed plugins. Obviously all approaches have drawbacks … they discussed the option of shipping their own package manager for Caddy plugins, too (shudder).
See: https://forum.caddyserver.com/t/packaging-caddy/61 https://forum.caddyserver.com/t/packaging-caddy/61
- singlow 9y agoNginx had the same issue. Ubuntu ships 3 or 4 versions - nginx-light, nginx, nginx-full, nginx-extras - for different numbers of modules included.
- dozzie 9y ago> [...] their problem was that Caddy plugins must be configured at compile-time, because runtime plugins seem to be hard to do with Golang [...] they'd either have to provide a slim package with no plugins, or ship with all or only some blessed plugins. Or ship the source in the package and build the target binary in the post-install. Or do what Debian does with Exim and nginx: provide several packages, each with different set of plugins compiled in. And these are just ideas from top of my head.
- overcast 9y agoYeh I've dug through that forum post a hundred times by now, the best option is the public script. https://getcaddy.com/ https://getcaddy.com/
- rrdharan 9y agogolang somewhat recently gained dynamic plugin support; wonder if that can be leveraged in Caddy? https://beta.golang.org/pkg/plugin/ https://beta.golang.org/pkg/plugin/
- CSDude 9y agoYes, but at the moment its only Linux