railway-deployment

Topics in the source

• Railway Deployment Management
• When to Use
• List Deployments
• Specify Service
• View Logs
• Deploy Logs
• Build Logs
• Logs for Failed/In-Progress Deployments

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 railway-environment skill with isDeleted: true. 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" Shows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging. In non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits. For debugging build failures or viewing build output. By default railway logs shows the last successful deployment. Use --latest for current: Formats: relative (30s, 5m, 2h, 1d, 1w) or ISO 8601 timestamps. Deploy logs: Build logs: Get deployment ID from railway deployment list. Note: The deployment ID is a positional argument, NOT --deployment . The --deployment flag is a boolean that selects deploy logs (vs --build for build logs). Redeploy the

This is an excerpt. Refer to the complete source and its current requirements.