Skip to content

Clarify Dockerfile path and root directory behavior#1157

Closed
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-dockerfile-root-directory
Closed

Clarify Dockerfile path and root directory behavior#1157
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-dockerfile-root-directory

Conversation

@radiantjade
Copy link
Copy Markdown
Contributor

Summary

  • clarify that dockerfilePath selects the Dockerfile only
  • note that it does not set the service Root Directory or Docker build context
  • point subdirectory Dockerfile users to the Root Directory service setting

Related Central Station question: https://station.railway.com/questions/set-root-directory-on-railway-toml-776939f0

Verification

  • git diff --check
  • pnpm exec content-collections build

Users can set a custom Dockerfile path through config as code or service variables, but that field only selects the Dockerfile. Add explicit guidance that it does not change the service Root Directory or Docker build context, so subdirectory Dockerfiles that expect local files should be paired with the service Root Directory setting.

Constraint: Railway config-as-code schema does not expose a rootDirectory field

Rejected: Add rootDirectory examples to railway.toml | unsupported by the public schema

Confidence: high

Scope-risk: narrow

Directive: Do not imply dockerfilePath changes build context unless the platform behavior changes

Tested: git diff --check; pnpm exec content-collections build

Not-tested: Full Next.js site build
@brody192 brody192 closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants