railway-deploy

Topics in the source

• Railway Deploy
• When to Use
• Modes
• Detach Mode (default)
• CI Mode
• Deploy Specific Service
• Deploy to Unlinked Project
• CLI Options

Deploy code from the current directory to Railway using railway up. 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) Starts deploy and returns immediately. Use for most deploys. Streams build logs until complete. Use when user wants to watch the build or needs to debug issues. 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 Default is linked service. To deploy to a different service: Deploy to a project without linking first: Requires both --project and --environment flags. | Flag | Description | |------|-------------| | -d, --detach | Don't attach to logs (default) | | -c, --ci | Stream build logs, exit when done | | -s, --service | Target service (defaults to linked) | | -e, --environment | Target environment (defaults to linked) | | -p, --project | Target project (requires --environment) | | [PATH] | Path to deploy (defaults to current directory) | Railway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked proje

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