railway-status

Topics in the source

• Railway Status
• When to Use
• When NOT to Use
• Check Status
• Handling Errors
• CLI Not Installed
• Not Authenticated
• No Project Linked

Check the current Railway project status for this directory. User asks about Railway status, project, services, or deployments User mentions deploying or pushing to Railway Before any Railway operation (deploy, update service, add variables) User asks about environments or domains Use the railway-environment skill instead when user wants: Detailed service configuration (builder type, dockerfile path, build command, root directory) Deploy config (start command, restart policy, healthchecks, predeploy command) Service source (repo, branch, image) Compare service configs Query or change environment variables Run: First verify CLI is installed: If command -v railway fails: Railway CLI is not installed. Install with: npm install -g @railway/cli or brew install railway Then authenticate: railway login If railway whoami fails: Not logged in to Railway. Run: railway login If status returns "No linked project": No Railway project linked to this directory. To link an existing project: railway link To create a new project: railway init Parse the JSON and present: Project: name and workspace Environment: current environment (production, staging, etc.) Services: list with deployment status Acti

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