The community maintains a list of the plugins they write, here in our wiki: List of Caddy 2 Modules
Thanks. I didn’t know this before. Maybe more exposure is needed?
Why do we have to build a whole CI service? Just choose an existing one of your liking and use that.
Because in my opinion maintaining a healthy plugin ecosystem could greatly boost the quality and quantity of plugins, as well as Caddy’s user base.
For caddy 1, the official downloader acted as poor man’s integration build tests for plugins, so non-developers can also consequently test whether plugins work well with the latest Caddy source and giving feedbacks to plugin devs. In Caddy 2 the feedback loop from a new Caddy release to downstream plugin developers can be much longer due to the lack of official web-based builders, so some plugins may cease working in silence.