railway-cloud-migration

Migrate JARVIS Hermes deployment from local WSL to Railway cloud.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill railway-cloud-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: railway-cloud-migration
Source: https://github.com/LamseyahElias/jarvis-cloud-v2/tree/main/hermes-agent/skills/devops/railway-cloud-migration
Command: npx skills add https://github.com/LamseyahElias/jarvis-cloud-v2 --skill railway-cloud-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates and coordinates the deployment of the JARVIS Hermes suite from local development (WSL) to Railway cloud, providing a centralized, scalable production environment.

Core Features & Use Cases

  • End-to-end migration planning for api-server, telegram-bot, hermes-agent, belditalk-worker, and postgres-db.
  • Phase-driven rollout with health checks, environment configuration, and feature enablement.
  • Use Case: Move existing workloads to Railway and validate with a staged deployment.

Quick Start

Deploy hermes-agent first on Railway, enable Telegram in Phase 2, and migrate scheduled tasks to Railway workers.

Frequently Asked Questions about railway-cloud-migration

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

FAQPage Schema
How do I migrate my local WSL deployment to Railway cloud?

Railway cloud migration automates moving the JARVIS Hermes suite from local WSL to a scalable production environment, coordinating API server, Telegram bot, agent, worker, and PostgreSQL deployment.

What is the best way to orchestrate a phased deployment on Railway for multiple services?

Phased deployment on Railway is orchestrated by deploying hermes-agent first, enabling Telegram in Phase 2, and migrating scheduled tasks to Railway workers while validating health checks at each step.

Do I need Dockerfiles in the hermes-agent root directory to deploy on Railway?

Yes, deploying on Railway requires Dockerfiles and root directories in hermes-agent, plus proper environment variables for API server, Telegram bot, and worker configuration.

How does health check validation work during a Railway cloud migration?

Health check validation works through stepwise rollouts with feature enablement at each phase, maintaining rollback readiness to revert if API server, worker, or database validation fails.

Can I migrate a Telegram bot and PostgreSQL database together to Railway?

Yes, migrating Telegram bot and PostgreSQL together to Railway is supported by configuring environment variables for both, enabling Telegram in Phase 2, and validating database connectivity.

What are the limitations of moving scheduled tasks to Railway workers?

Limitations include requiring proper environment variables and rollback readiness before migrating scheduled tasks, as stepwise rollout demands strict phase validation before full feature enablement.