Stop excluding scripts/ from the Docker build context - #4
Merged
Conversation
The cron service's `COPY scripts/ ./scripts/` failed because .dockerignore
excluded scripts/, so it was absent from the build context ("/scripts: not
found"). Drop the exclusion now that the image needs it for scripts/sync.py.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow-up to #3. That PR made the Dockerfile
COPY scripts/ ./scripts/(needed by the new Railway cron service), but.dockerignorestill excludedscripts/from the build context — the fix for this was pushed to the PR branch after it had already been merged, so it never landed onmain. Railway build failed with:Fix
Drop the
scripts/line from.dockerignoreso the directory is available toCOPY.🤖 Generated with Claude Code