a day ago
Is there a supported way to export the original source archive, or inspect the exact image already built from a Railway CLI upload, for a short-lived cron service? SSH does not manage to read the files before the instance exits, even when the deployment instance is observed as running.
We need to verify the exact deployed source before preparing a local change. We want to avoid restarting, redeploying, changing the cron or start command, or running the application against production data. Is there a supported download/export operation, or an isolated inspection workflow that reuses the immutable existing image without rebuilding from the current repository and without inheriting production variables or connections?
Please clarify any access requirements and costs before any new resources are created. This is a general platform question; no project identifiers, private code, logs or credentials are included.
1 Replies
a day ago
We don't have a download or export for a CLI upload's source archive, its build context, or the image built from it, and we can't pull those out for you. We also don't offer a separate inspection environment that runs an existing image without its production variables or connections.
The only way to get at those files is through a running container. You can use railway ssh, or scp/sftp against ssh.railway.com with an SSH key registered on your account, where the service's domain or a deployment instance ID is the username. Either one only works while that container is up. For a cron job that exits right away, that means there's no way to inspect it that also keeps its start command, schedule and deployment exactly as they are.
What the container holds also depends on how it was built. A multi-stage build keeps only the final stage, and compiled or bundled output isn't the original source. Neither of these routes creates new resources.
Status changed to Awaiting User Response Railway • 1 day ago