Skip to content
Inspecting an applied deployment without waking a sleeping service
s-takagi-s
OP

20 days ago

Hello Railway team,

We need a supported way to inspect the non-secret database connection identity of an existing application service’s currently applied deployment, without starting, waking, or restarting the application and without connecting to a database.

On a running application service, opening the dashboard Console changed the UI from “Disconnected” to “Connected” automatically, without a separate Connect action.

For another service, an earlier control-plane observation showed deployment status SLEEPING while its associated instance showed RUNNING. We have not opened that service’s Console to test its behavior.

Could you please clarify the following for ordinary application services, rather than Cloud Agents or new sandboxes?

  1. Can displaying the Console, its automatic connection, creating a terminal session, or executing a command wake/start/restart a service or create an instance? Is there a supported fail-if-sleeping mode?

  2. When deployment status is SLEEPING but the associated instance status is RUNNING, which status determines whether execution can occur in the existing container without starting the application?

  3. Do the deployment and instance IDs in the Console’s Full screen link bind the actual shell session, including automatic reconnects? Can it fail instead of selecting a different instance?

  4. Is there an official management function that returns only the DATABASE_URL hostname, port, database name, and configured role for a specified applied deployment snapshot, without runtime execution or a database connection? It must not return credentials, the raw connection string, or an entire variables map. If no such function exists, please confirm that limitation.

  5. For a separate, already-approved catalog-only audit, does Database View / Raw SQL support one persistent PostgreSQL backend, an explicit read-only transaction, a checkpoint after the first SELECT, and no automatic additional SQL or reconnection? If not, please identify the documented supported execution method.

We are requesting documentation and guidance only. Please do not execute commands or SQL, change settings or plans, create resources, or start, restart, or redeploy services on our behalf.

Thank you.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 20 days ago


Railway
BOT

20 days ago

Here is what we can confirm for ordinary application services.

Console, shell sessions and waking: shell access, whether the dashboard Console or railway ssh, opens a shell inside the service's running container. We can't confirm whether connecting or running a command wakes a sleeping service or causes a new instance to be created, so please don't rely on it not doing so. None of the documented railway ssh options is a fail-if-sleeping mode, and we can't point you to one in the dashboard.

SLEEPING deployment with a RUNNING instance: we can't confirm which of the two statuses decides whether a command can run in the existing container without starting the application.

Targeting: the CLI lets you pick a specific instance with railway ssh --deployment-instance <instance-id>, and a deployment instance ID also works as the SSH username for ssh, scp and sftp against ssh.railway.com. We can't confirm that the IDs in the Console's Full screen link pin the session, including automatic reconnects, or that it fails rather than selecting another instance. Note that railway ssh --session reconnects automatically and installs tmux in the container if it isn't already there.

Connection identity: we can't point you to a management function that returns only the hostname, port, database name and role behind DATABASE_URL for a specific applied deployment without returning variable values or the connection string.

Database View: the Database View is a management interface for browsing and editing tables and entries. We can't confirm that it holds one persistent backend, honors an explicit read-only transaction, pauses after the first SELECT, or avoids additional SQL and reconnects, so it shouldn't be relied on for an audit that needs those guarantees.


Status changed to Awaiting User Response Railway • 20 days ago


Railway
BOT

13 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 • 13 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...