feat: add XCADDY_NO_BUILD to not run go build #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mholt
requested changes
Nov 25, 2020
dunglas
force-pushed
the
feat/no-build
branch
from
38c5441
to
70a6197
Compare
dunglas
force-pushed
the
feat/no-build
branch
from
70a6197
to
e9fa593
Compare
|
I think you need a rebase, your changes seem to have removed some of the changes on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mercure and Vulcain now use Caddy. They are available as Caddy modules but also as standalone binaries build with GoReleaser.
I managed to use
xcaddyto prepare the source code andgoreleaserto cross-compile and package the binary: dunglas/mercure#398.Currently,
xcaddyalways compiles the project. This proposedXCADDY_NO_BUILDenvironment variable allows to prepare the source code but not rungo buildto save some CI time (go buildis run by GoReleaser).