fix(docker): un-ignore supabase/migrations (completes #149, unbreaks image build)#150
Merged
Merged
Conversation
The .dockerignore excluded the whole `supabase` dir, so the build stage had no supabase/migrations and the runtime COPY failed with '/app/supabase/migrations: not found'. Exclude only the Supabase local-dev assets (config/seed/snippets/templates) and keep migrations — the pg migration runner reads both postgres/migrations and supabase/migrations.
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.
Problem
#149 added
COPY --from=build /app/supabase/migrations …to the runtime image, but.dockerignorestill excludes the wholesupabasedir. So the build stage never receivessupabase/migrationsand the image build fails:This breaks the image build on
mainright now (staging redeploys fail — fail-safe, old release stays live).Fix
Replace the blanket
supabaseignore with:Excludes the Supabase local-dev assets (config.toml, seed.sql, snippets, templates) but keeps
supabase/migrations— which the pre-deploy migration runner reads (it applies bothpostgres/migrationsandsupabase/migrationsas one lineage).Together with #149
#149 + this = the Railway pre-deploy command
node scripts/migrate-postgres.mjsworks end-to-end: image carries the runner + full SQL lineage + pg, migrations apply before each release serves.