railway-environment

Topics in the source

• Environment Configuration
• Shell Escaping
• When to Use
• Create Environment
• Switch Environment
• Get Context
• Resolve Service ID
• Query Configuration

Query, stage, and apply configuration changes for Railway environments. CRITICAL: When running GraphQL queries via bash, you MUST wrap in heredoc to prevent shell escaping issues: Without the heredoc wrapper, multi-line commands break and exclamation marks in GraphQL non-null types get escaped, causing query failures. User wants to create a new environment User wants to duplicate an environment (e.g., "copy production to staging") User wants to switch to a different environment User asks about current build/deploy settings, variables, replicas, health checks, domains User asks to change service source (Docker image, branch, commit, root directory) User wants to connect a service to a GitHub repo User wants to deploy from a GitHub repo (create empty service first via railway-new skill, then use this) User asks to change build or start command User wants to add/update/delete environment variables User wants to change replica count or configure health checks User asks to delete a service, volume, or bucket User says "apply changes", "commit changes", "deploy changes" Auto-fixing build errors detected in logs Create a new environment in the linked project: Duplicate an existing environ

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