railway-database

Topics in the source

• Railway Database
• When to Use
• Decision Flow
• Check for Existing Databases
• Available Databases
• Prerequisites
• Adding a Database
• Step 1: Fetch Template

Add official Railway database services. These are maintained templates with pre-configured volumes, networking, and connection variables. For non-database templates, see the railway-templates skill. User asks to "add a database", "add Postgres", "add Redis", etc. User needs a database for their application User asks about connecting to a database User says "add postgres and connect to my server" User says "wire up the database" ALWAYS check for existing databases FIRST before creating. Before creating a database, check if one already exists. For full environment config structure, see environment-config.md. Then query environment config and check source.image for each service: The config.services object contains each service's configuration. Check source.image for: ghcr.io/railway/postgres or postgres: → Postgres ghcr.io/railway/redis or redis: → Redis ghcr.io/railway/mysql or mysql: → MySQL ghcr.io/railway/mongo or mongo: → MongoDB | Database | Template Code | |----------|---------------| | PostgreSQL | postgres | | Redis | redis | | MySQL | mysql | | MongoDB | mongodb | Get project context: Extract: id - project ID environments.edges[0].node.id - environment ID Get workspace ID (n

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