Take a stack that already works under `flisk up` to Railway with that host's own tooling - the Railway CLI or a connected repo, with variables set in Railway. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Railway. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Railway?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-railway)
---
name: flisk-deploy-railway
description: Take a stack that already works under `flisk up` to Railway with that host's own tooling - the Railway CLI or a connected repo, with variables set in Railway. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Railway. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Railway CLI or Git integration recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Railway
Flisk is local-only. This skill covers deploying to Railway.
## Workflow
1. Confirm the stack works locally with `flisk doctor && flisk up <stack>`.
2. Extract service contracts from service.json.
3. Connect the repo or use the Railway CLI.
4. Set environment variables and secrets in the Railway dashboard.
5. Deploy services (containers or buildpacks) and verify health endpoints.
## Guardrails
- Do not deploy local generated files.
- Keep production config separate from local service.json.
