cambium-railway-ops

Manage Cambio's GitHub-to-Railway deployments with schema checks and credential safeguards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-railway-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cambium-railway-ops
Source: https://github.com/ecnepsyroc-bot/Dejavara/tree/main/deploy/skills/cambium-railway-ops
Command: npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-railway-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies safe Railway deployment operations for the Cambium service to prevent production outages caused by hardcoded connection strings, schema drift, or mismanaged credentials during automated redeploys.

Core Features & Use Cases

  • Pre-push safety checklist: Require build, tests, rebase, and schema verification before pushing to main.
  • Variable reference enforcement: Ensure DATABASE_URL is the Railway Postgres variable reference to survive password rotations.
  • Schema validation and emergency repair: Run schema-checks and apply idempotent emergency fixes when critical columns are missing.
  • Post-deploy monitoring and rollback: Watch Railway logs, verify production login, and redeploy or revert faulty releases.
  • Credential rotation and recovery guidance: Procedures for Postgres password rotation, JWT key updates, and admin password recovery in emergencies.

Quick Start

Run the pre-push checklist, verify DATABASE_URL is set to the Railway Postgres variable reference, run the schema check, then push origin main and monitor the deployment logs.

Frequently Asked Questions about cambium-railway-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Railway deployment outages from hardcoded Postgres connection strings?

Prevent Railway deployment outages by enforcing DATABASE_URL as a Railway Postgres variable reference, ensuring your connection string survives credential rotations without breaking automated redeploys.

What is the pre-push safety checklist for deploying to Railway?

A pre-push safety checklist for Railway requires completing build, tests, rebase, and schema verification before pushing to main, preventing schema drift and production outages during automated GitHub-to-Railway deployments.

How do I handle schema drift and missing columns in a Railway Postgres deployment?

Handle schema drift by running schema checks before pushing to main and applying idempotent emergency fix scripts to repair missing critical columns in your Railway Postgres database.

How do I rotate Postgres passwords and JWT keys for a Railway deployment?

Rotate Postgres passwords and JWT keys for Railway deployments using established credential rotation procedures, which also cover admin password recovery and maintaining service uptime during updates.

What is the best way to monitor and rollback a faulty Railway release?

Monitor Railway deployment logs and verify production login post-deploy, then execute a redeploy or revert faulty releases using post-deploy rollback procedures to quickly restore service stability.

Do I need to verify Railway variables before every GitHub auto-deploy?

Yes, you need to verify Railway variable references like DATABASE_URL before every GitHub auto-deploy to ensure credentials are dynamically referenced and survive password rotations without downtime.