Can we include all plugins into the github builds until caddy’s build server allows to specify exact versions?
This would solve two problems of caddy’s AUR package:
- I could use hashes again to check the package integrity. Currently I can’t provide a hash because the build server maybe delivers a different (new) build each time.
- An URL with all plugins contained as query parameters is too long for the AUR server, which is clearly not a caddy issue, but forces me to use an URL shortener in the package build instructions.
I know there is already a proposal for a new build system but including all plugins in the pre-built github releases would solve all of my packaging issues right away.
Plugins contained in the pre-built github binaries:
Server types: http Caddyfile loaders: short flag default Other plugins: http.basicauth http.bind http.browse http.errors http.expvar http.ext http.fastcgi http.gzip http.header http.internal http.log http.markdown http.mime http.pprof http.proxy http.redir http.rewrite http.root http.status http.templates http.websocket shutdown startup tls tls.storage.file
A build with all plugins:
Server types: http Caddyfile loaders: short flag default Other plugins: http.awslambda http.basicauth http.bind http.browse http.cors http.errors http.expvar http.ext http.fastcgi http.filemanager http.git http.gzip http.header http.hugo http.internal http.ipfilter http.jwt http.locale http.log http.mailout http.markdown http.mime http.minify http.multipass http.pprof http.prometheus http.proxy http.ratelimit http.realip http.redir http.rewrite http.root http.search http.status http.templates http.upload http.websocket shutdown startup tls tls.dns.cloudflare tls.dns.digitalocean tls.dns.dnsimple tls.dns.dyn tls.dns.gandi tls.dns.googlecloud tls.dns.namecheap tls.dns.rfc2136 tls.dns.route53 tls.dns.vultr tls.storage.file