deploy
This skill should be used when the user wants to push code to Railway, says "railway up", "deploy", "ship", or "push". For initial setup or creating services, use new skill. For Docker images, use environment skill.
When & Why to Use This Skill
This Claude skill enables seamless code deployment to Railway directly through natural language commands. It automates the 'railway up' process, allowing developers to ship local changes, monitor real-time build logs in CI mode, and manage deployments across specific services or environments without leaving the chat interface. By streamlining the transition from code to cloud, it enhances developer productivity and simplifies the continuous delivery workflow.
Use Cases
- Rapidly deploying local code changes to Railway production or staging environments using simple triggers like 'ship' or 'deploy'.
- Debugging build failures by utilizing CI mode to stream real-time logs and identify issues with dependencies or environment configurations.
- Managing complex multi-service architectures by targeting specific services (e.g., 'deploy to backend') for isolated updates.
- Automating deployments for unlinked projects by providing specific project and environment IDs for a streamlined cloud setup.
- Executing 'deploy and fix' workflows where the agent monitors the build status and suggests immediate corrections upon failure.
| name | deploy |
|---|---|
| description | This skill should be used when the user wants to push code to Railway, says "railway up", "deploy", "deploy to railway", "ship", or "push". For initial setup or creating services, use new skill. For Docker images, use environment skill. |
| allowed-tools | Bash(railway:*) |
Deploy
Deploy code from the current directory to Railway using railway up.
When to Use
- User asks to "deploy", "ship", "push code"
- User says "railway up" or "deploy to Railway"
- User wants to deploy local code changes
- User says "deploy and fix any issues" (use --ci mode)
Modes
Detach Mode (default)
Starts deploy and returns immediately. Use for most deploys.
railway up --detach
CI Mode
Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.
railway up --ci
When to use CI mode:
- User says "deploy and watch", "deploy and fix issues"
- User is debugging build failures
- User wants to see build output
Deploy Specific Service
Default is linked service. To deploy to a different service:
railway up --detach --service backend
Deploy to Unlinked Project
Deploy to a project without linking first:
railway up --project <project-id> --environment production --detach
Requires both --project and --environment flags.
CLI Options
| Flag | Description |
|---|---|
-d, --detach |
Don't attach to logs (default) |
-c, --ci |
Stream build logs, exit when done |
-s, --service <NAME> |
Target service (defaults to linked) |
-e, --environment <NAME> |
Target environment (defaults to linked) |
-p, --project <ID> |
Target project (requires --environment) |
[PATH] |
Path to deploy (defaults to current directory) |
Directory Linking
Railway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.
For subdirectory deployments, prefer setting rootDirectory via the environment skill, then deploy normally with railway up.
After Deploy
Detach mode
Deploying to <service>...
Use deployment skill to check build status (with --lines flag).
CI mode
Build logs stream inline. If build fails, the error will be in the output.
Do NOT run railway logs --build after CI mode - the logs already streamed. If you need
more context, use deployment skill with --lines flag (never stream).
Composability
- Check status after deploy: Use
serviceskill - View logs: Use
deploymentskill - Fix config issues: Use
environmentskill - Redeploy after config fix: Use
environmentskill
Error Handling
No Project Linked
No Railway project linked. Run `railway link` first.
No Service Linked
No service linked. Use --service flag or run `railway service` to select one.
Build Failure (CI mode)
The build logs already streamed - analyze them directly from the railway up --ci output.
Do NOT run railway logs after CI mode (it streams forever without --lines).
Common issues:
- Missing dependencies → check package.json/requirements.txt
- Build command wrong → use environment skill to fix
- Dockerfile issues → check dockerfile path