deployment

Manage Railway deployments, view logs, and debug deployment failures via CLI commands.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill deployment-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/deployment
Command: npx skills add https://github.com/sethdavis512/iridium --skill deployment-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing Railway deployments manually requires memorizing CLI flags and log filtering syntax, and debugging failed deploys often means digging through build and runtime logs without clear guidance. ## Core Features & Use Cases - Deployment Lifecycle Control: List, redeploy, restart, or remove deployments using railway CLI commands with service and environment targeting. - Log Inspection & Filtering: Fetch deploy or build logs with line limits, time ranges, text filters, and per-deployment queries for debugging. - Troubleshooting Guidance: Diagnose build failures and runtime crashes with structured log presentation and error summaries. - Use Case: A service crashes after a config change. List recent deployments, pull the latest logs filtered for errors, identify the stack trace, then redeploy or restart the service. ## Quick Start Show me the last 100 error logs for my Railway backend service and redeploy it.

Frequently Asked Questions about deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view Railway deployment logs from the CLI?▼

Run railway logs with the --lines flag to fetch deploy logs, or add --build for build logs. Use --latest to see the most recent deployment even if it failed, and --json for structured output.

How do I filter Railway logs for errors?▼

Use the --filter flag with query syntax, such as railway logs --filter "@level:error" for errors only. You can combine conditions like "@level:error AND timeout" and use --since and --until for time-based filtering.

What is the difference between railway down and deleting a service?▼

railway down removes the current deployment but keeps the service intact, so it can be redeployed later. To delete a service entirely, use the environment skill with isDeleted set to true, which requires admin permissions.

How do I redeploy or restart a Railway service without new code?▼

Use railway redeploy --service <name> -y to redeploy the most recent deployment, or railway restart --service <name> -y to restart the container without rebuilding. Restart is useful when external resources changed but code did not.

Why does railway logs show an old deployment instead of the failed one?▼

By default railway logs shows the last successful deployment. Add the --latest flag to view logs from the most recent deployment even if it failed, or pass a specific deployment ID as a positional argument.