Skip to content
How can I recover or verify source uploaded for a deployment?
sebastiangonzalez1958
OP

a month ago

For a deployment created by uploading local source, is there a supported way to retrieve the retained source archive or file manifest?

How is the build-input snapshot hash calculated—including file ordering, path normalization, exclusions and metadata—so an original local archive can be checked reproducibly?

Solved

1 Reply

Railway
BOT

a month ago

There's no self-serve way to download the source archive, build context, or file manifest behind an uploaded deployment, and we don't hand these back on request. The snapshot hash isn't something we offer as a way to check a local archive against a deployment.

The one route we support is the running container itself. Whatever was copied into the image is on its filesystem, so you can compare it against your local copy. You can browse and download files from the service's Console tab, or pull a whole directory with scp -r / sftp through ssh.railway.com once you've added an SSH key (railway ssh keys add). Keep in mind that a multi-stage build only keeps the final stage, and files your .railwayignore excluded were never uploaded.

If no deployment is running, a recent previous deployment can be restored with Rollback while it's still inside your plan's image retention window. That brings a container back up so you can inspect its files.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...