fix(docker): restore DATABASE_URL build ARG for prisma generate#5
Merged
Conversation
…risma generate prisma.config.ts (Prisma 7+) resolves env(DATABASE_URL) at config load time, so even `prisma generate` fails with PrismaConfigEnvError if the variable is unset. Restore ARG DATABASE_URL but default it to a dummy localhost URL so the build succeeds without depending on Railway injecting a secret build arg. The real DATABASE_URL is still injected by Railway as a runtime env var, the runtime container reads it from process.env at startup. Co-Authored-By: Claude Opus 4.7 <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.
Hotfix for Railway build failure introduced by #4.
prisma.config.ts(Prisma 7+) resolvesenv(DATABASE_URL)at config load time, so evenprisma generateneeds the var to be defined. My audit fix dropped the ARG thinking onlymigrate deployneeded it — wrong for the config-file flow.Restored
ARG DATABASE_URLwith a dummy default (postgresql://build:build@localhost:5432/build). Build succeeds without Railway secrets. Runtime still reads the real one fromprocess.envat startup, untouched.The other hardening from #4 (USER node, HEALTHCHECK, .dockerignore, --chown) stays in place.