Deployment
Let your coding agent list Railway deployments, pull build and deploy logs, redeploy or restart, or take down the active release without deleting the service.
Overview
deployment is an agent skill for the Operate phase that manages Railway deployment lifecycle, visibility, and log-based troubleshooting via the Railway CLI.
Install
npx skills add https://github.com/railwayapp/railway-skills --skill deploymentWhat is this skill?
- Bash-only Railway CLI (`railway:*`) for list, logs, redeploy, restart, and `railway down`
- JSON deployment list with optional `--service` and `--limit` for targeting IDs
- Separate deploy logs and build logs with `--lines` and non-interactive fetch
- `railway down` removes the current deployment but keeps the service (full delete uses environment skill)
- deployment list supports --limit (e.g. 10)
- logs fetch supports --lines (e.g. 100)
Adoption & trust: 1k installs on skills.sh; 274 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app is on Railway but you cannot list deployment history, restart a bad release, or read build and deploy logs from inside your agent session.
Who is it for?
Indie builders shipping APIs or SaaS on Railway who want agent-driven redeploys and incident log checks without leaving the terminal.
Skip if: Creating new Railway projects, provisioning environments, or permanently deleting services—those flows are outside this skill’s scope.
When should I use this skill?
User wants to manage Railway deployments, view logs, redeploy, restart, remove a deployment, or debug deploy/build failures—not delete entire services.
What do I get? / Deliverables
You get structured deployment lists, log excerpts, and safe redeploy or stop actions while keeping the underlying Railway service intact unless you use a different skill to delete it.
- Deployment list and status metadata
- Deploy and build log excerpts
- Redeploy, restart, or stop-deployment actions
Recommended Skills
Journey fit
Deployment lifecycle and log triage happen after go-live when services are already running in production. Canonical shelf is infra because the skill wraps Railway CLI for redeploy, stop, list, and history—not greenfield provisioning.
How it compares
Railway-specific deployment and log commands via a skill, not a generic Docker Compose or Terraform deploy tutorial.
Common Questions / FAQ
Who is deployment for?
Solo and indie builders already using Railway who want their coding agent to operate deployments and read logs during ship and operate work.
When should I use deployment?
Use it when you need to redeploy, restart, list deployment history, stream deploy or build logs, or debug why a Railway release failed—typically in Operate (infra/errors) right after or between Ship launches.
Is deployment safe to install?
Review the Security Audits panel on this Prism page before granting Bash access to `railway:*`; the skill can stop deployments and trigger redeploys on linked projects.
SKILL.md
READMESKILL.md - Deployment
# Deployment Management Manage existing Railway deployments: list, view logs, redeploy, or remove. **Important:** "Remove deployment" (`railway down`) stops the current deployment but keeps the service. To delete a service entirely, use the `environment` skill with `isDeleted: true`. ## When to Use - User says "remove deploy", "take down service", "stop deployment", "railway down" - User wants to "redeploy", "restart the service", "restart deployment" - User asks to "list deployments", "show deployment history", "deployment status" - User asks to "see logs", "show logs", "check errors", "debug issues" ## List Deployments ```bash railway deployment list --limit 10 --json ``` Shows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging. ### Specify Service ```bash railway deployment list --service backend --limit 10 --json ``` ## View Logs ### Deploy Logs ```bash railway logs --lines 100 --json ``` In non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits. ### Build Logs ```bash railway logs --build --lines 100 --json ``` For debugging build failures or viewing build output. ### Logs for Failed/In-Progress Deployments By default `railway logs` shows the last successful deployment. Use `--latest` for current: ```bash railway logs --latest --lines 100 --json ``` ### Filter Logs ```bash # Errors only railway logs --lines 50 --filter "@level:error" --json # Text search railway logs --lines 50 --filter "connection refused" --json # Combined railway logs --lines 50 --filter "@level:error AND timeout" --json ``` ### Time-Based Filtering ```bash # Logs from last hour railway logs --since 1h --lines 100 --json # Logs between 30 and 10 minutes ago railway logs --since 30m --until 10m --lines 100 --json # Logs from specific timestamp railway logs --since 2024-01-15T10:00:00Z --lines 100 --json ``` Formats: relative (`30s`, `5m`, `2h`, `1d`, `1w`) or ISO 8601 timestamps. ### Logs from Specific Deployment Deploy logs: ```bash railway logs <deployment-id> --lines 100 --json ``` Build logs: ```bash railway logs --build <deployment-id> --lines 100 --json ``` Get deployment ID from `railway deployment list`. **Note:** The deployment ID is a positional argument, NOT `--deployment <id>`. The `--deployment` flag is a boolean that selects deploy logs (vs `--build` for build logs). ## Redeploy Redeploy the most recent deployment: ```bash railway redeploy --service <name> -y ``` The `-y` flag skips confirmation. Useful when: - Config changed via environment skill - Need to restart without new code - Previous deploy succeeded but service misbehaving ### Restart Container Only Restart without rebuilding (picks up external resource changes): ```bash railway restart --service <name> -y ``` Use when external resources (S3 files, config maps) changed but code didn't. ## Remove Deployment Takes down the current deployment. The service remains but has no running deployment. ```bash # Remove deployment for linked service railway down -y # Remove deployment for specific service railway down --service web -y railway down --service api -y ``` This is what users mean when they say "remove deploy", "take down", or "stop the deployment". **Note:** This does NOT delete the service. To delete a service entirely, use the `environment` skill with `isDeleted: true`. ## CLI Options ### deployment list | Flag | Description | |------|-------------| | `-s, --service <NAME>` | Service name or ID | | `-e, --environment <NAME>` | Envir