@JeanMarie-TTS and I determined that as of Caddy v2, everything is under the Apache license and there don't appear to be any restrictions on redistribution of binaries. So we can include our custom binary in the tree now! However, we don't want it to go out of date.
This PR adds a workflow to try building the binary every day (or when manually triggered), and then make a PR if the binary differs from what was already there.
@JeanMarie-TTS and I determined that as of Caddy v2, everything is under the Apache license and there don't appear to be any restrictions on redistribution of binaries. So we can include our custom binary in the tree now! However, we don't want it to go out of date.
This PR adds a workflow to try building the binary every day (or when manually triggered), and then make a PR if the binary differs from what was already there.