Repository navigation
Restore the from-source Dockerfile for Railway branch builds - #1086
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
nick-potts
added a commit
that referenced
this pull request
Sep 30, 2026
* Restore the from-source Dockerfile so Railway can build any branch * Document the from-source Dockerfile --------- Co-authored-by: Codex <codex@codex-vm.tailcb9c5.ts.net>
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
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.
Summary
Brings back the from-source
Dockerfilethat #1063 removed, so Railway can build and deploy any branch without CI publishing an image first./ +├── Dockerfile # from source: Rust SDK → pnpm build → runtime (Railway builds branches) └── Dockerfile.cloud # runtime only: packages CI's prebuilt output (production, unchanged)The file is identical to the one before #1063, including the Railway cache mounts keyed to the
webservice ID. That ID is the same in every Railway environment, so staging and PR environments share the caches.Production is unchanged: it still runs the
ghcr.io/getployz/ployz2-cloud:mainimage that CI publishes.Evidence
stagingenvironment buildingwebfromprototype/build-order-dashboardfailed: "The configured root directory was not found in the deployed source". The error was misleading; the actual cause was that noDockerfileexisted.After: the same branch with this file restored, on top of current main, built from source on Railway and deployed:
staging web: SUCCESS … prototype/build-order-dashboard eacca201, serving HTTP 200. The build ran all three stages (Rust SDK,pnpm build:app, runtime) and the new single-baseline migration.Merge Danger
Door: two-way
A new file plus two README lines; nothing in CI or production reads it.
Blast Radius: none
Only Railway services that build from source with dockerfile path
/Dockerfileuse it.