railway-new

Topics in the source

• New Project / Service / Database
• When to Use
• Prerequisites
• Decision Flow
• Check Current State
• When Already Linked
• Parent Directory Linking
• Init vs Link Decision

Create Railway projects, services, and databases with proper configuration. User says "deploy to railway" (add service if linked, init if not) User says "create a railway project", "init", "new project" (explicit new project) User says "link to railway", "connect to railway" User says "create a service", "add a backend", "new api service" User says "create a vite app", "create a react website", "make a python api" User says "deploy from github.com/user/repo", "create service from this repo" User says "add postgres", "add a database", "add redis", "add mysql", "add mongo" User says "connect to postgres", "wire up the database", "connect my api to redis" User says "add postgres and connect to the server" Setting up code + Railway service together Check CLI installed: If not installed: Install Railway CLI: npm install -g @railway/cli or brew install railway Check authenticated: If not authenticated: Run railway login to authenticate. If linked: Add a service to the existing project (see below) If not linked: Check if a PARENT directory is linked (see below) Default behavior: "deploy to railway" = add a service to the linked project. Do NOT create a new project unless user EXPLICITLY s

This is an excerpt. Refer to the complete source and its current requirements.