Shell access and one-off jobs
Inspect a running application or execute a tracked command using its release environment.
Openstead provides two ways to execute application commands: an interactive shell inside a running instance and a one-off command in a fresh execution container. Both require an eligible active paid application service and permission to operate it.
Open an interactive shell
- Open the service's Shell page.
- Select an available instance if the service has several.
- Connect and run the diagnostic command.
- Disconnect when finished.
The session is attached to the selected live instance. It can inspect files and mounted data visible to that instance. Commands can change production state, so treat the shell with the same care as application administration.
Sessions expire after 20 minutes. An account can have two active terminal sessions at a time. If a deployment replaces the instance, refresh the instance list and reconnect.
Run a one-off command
Use Run a command or One-Off Jobs for a command that should execute with the current release image and environment and retain its output and exit status.
Examples include:
python manage.py check --deployphp artisan migrate:statusEach one-off command runs in a fresh container with access to the permitted private network. It does not share the running application's writable filesystem or persistent disk. Files created in that execution are not a way to update the deployed application's source or upload directory.
Use a deployment's pre-deploy command for migrations that must gate a release. Use a cron job for a repeating schedule.
Availability by service
| Service | Interactive shell | One-off application commands |
|---|---|---|
| Paid running web service, private service, or worker | Yes, when a live instance is available | Yes |
| Static release | No application container | No application container |
| Cron job | No permanent instance | Use its run controls and history |
| Managed database | No application shell | Use its database connection or management tools |
| Free web instance | Requires an upgrade | Requires an upgrade |
For MySQL administration, see MySQL. Do not use application shell credentials as a replacement for database access controls.
Make lasting changes through deployments
Editing source code in a shell is temporary and bypasses your repository history. Commit the change to Git and deploy it. Store durable application data in its database, persistent disk, or object storage, and take an appropriate backup before changing production records.