railway-docs

Fetches up-to-date Railway documentation to answer platform questions accurately.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill railway-docs-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: railway-docs
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/railway-docs
Command: npx skills add https://github.com/sethdavis512/iridium --skill railway-docs-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Railway's platform evolves quickly, and answering questions from memory risks outdated or incorrect information about deployments, variables, builders, and pricing. This Skill fetches current Railway documentation so answers reflect the live docs. ## Core Features & Use Cases - LLM-optimized doc sources: Pulls from Railway's llms.txt endpoints and appends .md to any docs.railway.com URL for clean, parseable content. - Configuration references: Includes detailed references for EnvironmentConfig JSON patches, monorepo deployment strategies, Railpack builder detection, and variable templating syntax. - Use Case: A user asks how to deploy a pnpm monorepo with shared packages on Railway. The Skill consults the monorepo reference to recommend custom build commands with watch paths instead of a root directory, avoiding broken builds. ## Quick Start Ask how to configure replicas across regions on Railway and have the current docs fetched to answer.

Frequently Asked Questions about railway-docs

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

FAQPage Schema
How do I deploy a monorepo to Railway?▼

Railway supports isolated monorepos via the Root Directory setting and shared monorepos via custom build and start commands. For shared TypeScript workspaces, leave root directory empty and use commands like pnpm --filter backend build, plus watch paths to avoid unnecessary rebuilds.

How do I set environment variables on Railway services?▼

Set variables by applying an EnvironmentConfig JSON patch with the CLI command railway environment edit --json. Variables support references like ${{shared.DOMAIN}} or ${{Postgres.DATABASE_URL}} to wire services together, and setting a variable to null deletes it.

Does Railpack support my framework or language?▼

Railpack auto-detects Node, Python, Go, PHP, Java, Ruby, Rust, Elixir, Gleam, Deno, and static sites. It recognizes frameworks like Next.js, Vite, Astro, Django, and FastAPI, generating appropriate build and start commands without configuration.

Should I use public or private domains between Railway services?▼

Use private domains for service-to-service and service-to-database communication since they are faster, avoid egress costs, and are more secure. Use public domains only when browsers or external webhooks need access, since they cannot reach the private network.

Why is my Railway monorepo build failing with shared packages?▼

Setting a root directory makes code outside that directory unavailable during builds, breaking imports from shared packages. Remove the root directory and use workspace filter commands like pnpm --filter or turbo run build --filter instead.