From e8903d25f0aa7783d0b3f60ce540949a9ed016e7 Mon Sep 17 00:00:00 2001 From: radiantjade Date: Fri, 15 May 2026 16:33:06 +0900 Subject: [PATCH] Clarify build cache troubleshooting The build configuration page explained how to disable layer caching, but not what that switch does not affect. Add the missing boundary so users checking apparently stale files also verify the linked repo, branch, root directory, Dockerfile path, and watch paths. Constraint: Central Station bounty describes stale build fragments and old files being used Rejected: Add a support-specific workaround | the durable docs value is clarifying the cache boundary Confidence: medium Scope-risk: narrow Tested: git diff --check; pnpm exec content-collections build --- content/docs/builds/build-configuration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/docs/builds/build-configuration.md b/content/docs/builds/build-configuration.md index 33bd3a4da..09b9318fa 100644 --- a/content/docs/builds/build-configuration.md +++ b/content/docs/builds/build-configuration.md @@ -123,6 +123,12 @@ in your service: NO_CACHE=1 ``` +This forces Railway to rebuild layers instead of reusing cached build output. +It does not change which repository, branch, root directory, or Dockerfile is +used for the deployment. If a build appears to use stale or unexpected files, +also check the service's linked repository, branch, [root directory](#set-the-root-directory), +Dockerfile path, and watch paths before redeploying. + ## Why isn't my build using cache? Since Railway's build system scales up and down in response to demand, cache hit