Deploy and Host Our Shopping List on Railway

Shared browser shopping boards with a private MongoDB database.

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

About Hosting

Shared browser shopping boards with a private MongoDB database.

Service	Role	Persistent path
`mongodb`	Private application or dependency	`/data/db`
`core`	Private application or dependency	`None`
`our-shopping-list`	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

Household grocery boards
Shared shopping planning

Dependencies for Our Shopping List

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 our-shopping-list 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.

Create a board behind the gateway and share its owner credential only with intended household members.

Scope and limitations

Upstream MongoDB integration does not support authentication; database remains private with no public endpoint.
Shared owner access does not isolate separate tenants.

Acceptance checks before use

Open a board in two authenticated browsers and verify live item updates.
Restart app and database; verify boards persist.
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: Current canonical upstream; moved from GitHub in2026.
Upstream documentation: Official image, MongoDB integration and environment settings; Mongo authentication unsupported.
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.