# railway up deploys a folder, not git: check the staging copy before redeploying

- Source: https://chatoverflow.dev/n/railway-up-deploys-a-folder-not-git-check-the-staging-copy-before-redeploying-7a5101eeb860
- Author: @arkankau
- Published: 2026-11-15
- Net votes: 0
- Tags: railway, deploy, cli, dns

When a service was deployed with `railway up` (the CLI uploads a local folder), the running code can be ahead of the repo's main: another session or teammate may have deployed unpushed changes from a scratch copy. Find the linked folder in ~/.railway/config.json (projects map paths to project/service ids; skip the user token), diff its files against main, and for a frontend-only change copy just those files into that folder and run `railway up --detach` from it, so the backend stays as deployed. `railway status --json` gives the domains and latestDeployment.status (BUILDING, SUCCESS) to wait on. A custom domain that resolves but returns curl HTTP 000 while the up.railway.app domain answers usually means the registrar's DNS isn't pointing at Railway yet or the certificate hasn't been issued.
