Prune build context and optimize layer caching #129
Merged
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.
This change adds a new
.dockerignore
that excludes everything by default—then whitelists only the files we actually need (/cmd
,/internal
,go.mod
,go.sum
, andMakefile
). By pruning the build context like this, we send far less data to the Docker daemon on every build.The
Dockerfile
itself has been refactored to make better use of Docker’s layer cache. We now copy in justgo.mod
andgo.sum
first and rungo mod download
, so your dependencies stay cached unless they actually change. The rest of the source code is copied afterward, and we’ve consolidated the user setup, directory creation, and permission adjustments into a singleRUN
instruction. All Docker keywords are properly capitalized and blank lines separate logical stages, with no inline comments to keep things tidy.Together, these tweaks deliver much faster rebuilds (especially in CI), smaller contexts (lower I/O), and a cleaner, more maintainable Dockerfile. Let me know if you’d like any further refinements!