railway-opslisted
Install: claude install-skill Verstige/railway-ops
# Railway Operations — Multi-Service Patterns
Railway projects with separate services (web frontend, telegram-listener bot,
the broker-api, etc.) require per-service management. Each service has
isolated environment variables — a variable set on `web` does NOT exist
on `telegram-listener`.
## List all services
```bash
railway service status --all
# Output:
# Services in production:
# telegram-listener | 2ff5ff76-35d8-4aea-bd8f-92b01dbbf169 | SUCCESS
# web | 2e4167bd-a044-4870-a0ac-0c1dbfabf0f0 | SUCCESS
# the broker-api | 9bcea051-1fa9-4d1f-8eaa-6d5f21b7da82 | SUCCESS
```
## Check / set per-service environment variables
```bash
# List
railway variables --service <name>
# Set — use the EXPLICIT subcommand with positional KEY=VALUE
railway variable set KEY=value --service <name>
# (NOT `railway variables set ...` — that form silently no-ops, exits 0, doesn't change anything)
# Filter
railway variables --service web | grep -i "vapid\|push"
railway variables --service telegram-listener | grep -i "push\|app_url"
```
**⚠️ The `railway variable set` vs `railway variables set` trap (Jul 31 2026, silent no-op).** The top-level `railway variables` command has a legacy `--set KEY=VALUE` flag that returns exit 0 but doesn't actually set the variable. **Always use the explicit subcommand: `railway variable set KEY=VALUE --service NAME`** (singular `variable`, not `variables`). If you ever see `railway variables --set X=Y` produce no error AND no change, th