Railway Deploy

Deploys Gravity Claw to Railway using a pause, type-check, deploy, verify cycle.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/brittb-dev/zerogravityclaw --skill railway-deploy-brittb-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Railway Deploy
Source: https://github.com/brittb-dev/zerogravityclaw/tree/main/.agent/skills/railway-deploy
Command: npx skills add https://github.com/brittb-dev/zerogravityclaw --skill railway-deploy-brittb-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a Telegram bot to Railway risks message conflicts when local and live instances poll the same token, and broken builds when type errors slip through. This Skill enforces a disciplined pause → test → deploy → verify workflow to prevent those failures. ## Core Features & Use Cases - Conflict Prevention: Always pauses the live Railway service with railway down before local testing so two bot instances never fight over the same Telegram token. - Pre-Deploy Validation: Runs npx tsc --noEmit to catch TypeScript errors before pushing code. - Deployment & Verification: Deploys with railway up --detach and confirms health via railway logs, plus manages environment variables like TELEGRAM_BOT_TOKEN and GROQ_API_KEY. - Use Case: You fixed a bug in your Telegram bot locally. Use this Skill to pause the live bot, type-check, redeploy to Railway, and verify the logs show a clean startup. ## Quick Start Deploy my Gravity Claw bot to Railway using the standard pause, type-check, deploy, and verify cycle.

Frequently Asked Questions about Railway Deploy

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

FAQPage Schema
How do I deploy a Telegram bot to Railway?▼

Deploy a Telegram bot to Railway by running railway down to pause the live service, npx tsc --noEmit to type-check, railway up --detach to deploy, and railway logs --lines 40 to verify a clean startup.

How to set environment variables on Railway?▼

Set environment variables on Railway with railway variables set KEY="value", and list existing ones with railway variables. Required variables include TELEGRAM_BOT_TOKEN, GROQ_API_KEY, and ALLOWED_USER_IDS.

Why is my Telegram bot receiving messages in the wrong place?▼

This happens when two bot instances poll the same Telegram token simultaneously. Run railway down to pause the live service before starting local development with npm run dev.

Why did my Railway build fail?▼

Railway builds usually fail due to npm or TypeScript errors. Check railway logs --lines 100 for details, and run npx tsc --noEmit locally before deploying to catch type errors early.

Does Railway persist local files between deploys?▼

No, the Railway filesystem is ephemeral, so the data/ directory including dashboard settings and activity logs resets on every deploy. Use environment variables for any configuration that must persist.