Deploy and Host NutriTrace Personal Tracker on Railway

Private nutrition and food records with SQLite and uploads.

Draft status: Configuration and upstream documentation reviewed. Container startup, Railway application workflows, restart behavior, backup restoration and costs remain unverified.

About Hosting

Private nutrition and food records with SQLite and uploads.

Service	Role	Persistent path
`core`	Private application or dependency	`/data`
`nutritrace`	Public owner gateway	`None`

Why Deploy

Run this application in your own Railway project, with explicit configuration and storage under your control.

Common Use Cases

Personal nutrition and food records

Dependencies for NutriTrace Personal Tracker

Deployment Dependencies

The application images are pinned by registry digest. Database services, when included, stay on the private network. One replica is supported for each volume-backed service.

First use

Open the nutritrace service's HTTPS domain. Sign in to the owner gateway with username admin and its generated ACCESS_PASSWORD. Complete the application's own setup afterward.

API calls must also send X-Template-Key with that owner password. The gateway forwards native Bearer tokens, strips Basic Authorization, and limits requests to 32 MiB. Browser sessions receive a secure owner cookie. Native clients, webhooks and public sharing require specific compatibility checks before use. Gateway /healthz only checks the proxy, not application readiness.

Complete first-run setup behind the owner gateway and create the application administrator.

Scope and limitations

Browser-only draft. Native clients, public sharing and external MCP access are not configured.
Optional AI, SMTP and OIDC integrations require operator configuration. Retain JWT_SECRET and TOKEN_ENC_KEY with backups.
The optional large Open Food Facts database mirror is not included.

Acceptance checks before use

Complete setup, create a record and attach a small image.
Restart and verify record and attachment persistence.
Confirm generated credentials are distinct on a second fresh deployment.
Back up every listed persistent path and database, then restore into a separate test project.
Measure Railway usage with representative data and workload before estimating operating costs.

Backups and upgrades

Back up databases, file volumes, encryption keys and configuration together. Keep a copy outside the running project. Review upstream migration notes before changing a digest; rollback can require restoring a compatible database and files, not just selecting an older image.

Sources and selection evidence

Upstream documentation: Official DockerHub mirror, port, DB_PATH, UPLOADS_PATH and secrets.
Upstream documentation: Official single-container deployment layout.
Upstream project

Product and alias searches found no matching public Railway listing during this research. This is a bounded search result; private, unindexed or differently named listings may exist. It is not evidence of demand or revenue.

Upstream software retains its own license and edition restrictions. This deployment draft does not imply upstream endorsement.