-Nothing to do by hand. At boot the hub builds the sidecar template: Railway's standard image, Bun 1.4.2 from its official Linux x64 release archive, checked against the SHA-256 Bun publishes for it in the release's `SHASUMS256.txt` (the value in the code was checked against that file; the same Bun as the hub's image, `oven/bun:1.4.2`), the repository at `SANDBOX_COMMIT_SHA` checked out at `/app`, as in the hub's image, its dependencies installed, and oxlint for the code review's lint step. Railway caches the build by its content, so each new hub version builds once; the hub logs `railway_sidecar_template_built`, or `railway_sidecar_template_failed` with the reason. No sandbox is created before the build is done: a sidecar requested earlier waits for it, and if the hub stops waiting first, the provisioner answers `template_not_ready` and the hub tries again. A failed build is tried again by the next sidecar requested.
0 commit comments