Deploy and Host Tandoor on Railway

Deploy Tandoor on Railway with a digest-pinned application image, PostgreSQL 16, and persistent storage for recipe media and database data. The template exposes the web application through Railway while keeping its database connection within the Railway project.

What is Tandoor?

Tandoor, also known as Tandoor Recipes, is an open-source recipe manager for collecting and organizing recipes, planning meals, creating shopping lists, and sharing a household recipe collection. Its responsive web interface includes recipe imports, cookbooks, tags, search, and user management.

About Hosting Tandoor

This community template runs Tandoor 2.6.13 from the official digest-pinned container image alongside a digest-pinned PostgreSQL 16 Alpine container. Railway exposes Tandoor on public port 80 and checks application health at /. PostgreSQL is used by Tandoor over Railway's internal service network. Uploaded media persists at /opt/recipes/mediafiles, and PostgreSQL data persists at /var/lib/postgresql/data.

Database connection values are passed to Tandoor with Railway service references rather than copied credentials. Sensitive application values are generated when the template is deployed. Keep those reference and generated-variable semantics intact when editing the template; do not replace them with shared literal credentials or commit resolved values to source control.

Why Deploy Tandoor on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Tandoor on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Common Use Cases

Collect and organize recipes from websites and personal sources.
Plan household meals and create shopping lists.
Share recipes, cookbooks, and tags with family or a small team.

Dependencies for Tandoor Hosting

Tandoor image: vabene1111/recipes:2.6.13@sha256:f6c58afdea7a721d079ebd6ee5483f2c9da77dd1e709e16d60a82c218e80a451
PostgreSQL image: postgres:16-alpine@sha256:16bc17c64a573ef34162af9298258d1aec548232985b33ed7b1eac33ba35c229
A Tandoor volume mounted at /opt/recipes/mediafiles.
A PostgreSQL volume mounted at /var/lib/postgresql/data.

Persistent volumes protect application state across normal restarts and redeployments, but they are not a substitute for tested backups. Back up the PostgreSQL data and uploaded media together before an upgrade. Rolling the application image back does not reverse database migrations; if an upgrade is incompatible, restore matching database and media backups before starting the previous pinned image.