Deploy and Host Readeck on Railway

Readeck is a lightweight, self-hosted read-it-later service — a Pocket replacement that saves the full readable content of web pages as permanent, immutable archives. This template deploys it on Railway with persistent storage, ready for browser extensions, the iOS client, and KOReader e-reader sync.

About Hosting readeck-railway

Readeck publishes its official container image to Codeberg's registry, which Railway's direct image deploys don't support — so this template builds from a one-line Dockerfile shim that pulls the official image at build time. The template provisions a persistent volume at /readeck holding the SQLite database, configuration, and every archived article, so redeploys and upgrades never touch your data. Serverless is disabled via railway.json because read-later clients sync in short bursts and handle cold starts poorly. After deploying, open the service URL, create your admin account, and connect your clients. Total setup is a few minutes.

Common Use Cases

Personal Pocket/Omnivore replacement: save articles from browser extensions, iOS share sheet, or the API, and read them anywhere with highlights and annotations
E-ink reading pipeline: sync saved articles to Kindle, Kobo, and other KOReader devices via the Readeck KOReader plugin, with archive-on-finish flowing back to the server
Permanent web archive: every bookmark is stored as an immutable ZIP with full content and images, immune to link rot and paywall changes

Dependencies for readeck-railway Hosting

Readeck official container image (codeberg.org/readeck/readeck)
A Railway volume mounted at /readeck (provisioned by this template)

Deployment Dependencies

Implementation Details

The entire bridge between Codeberg's registry and Railway is:

FROM codeberg.org/readeck/readeck:latest

ENV READECK_SERVER_HOST=0.0.0.0 \
    READECK_SERVER_PORT=8000

WORKDIR /readeck
EXPOSE 8000

WORKDIR /readeck materializes the data directory as an image layer, which Railway's runtime requires. If you front the service with a custom domain, set the optional template variables READECK_SERVER_BASE_URL (https://your.domain) and READECK_ALLOWED_HOSTS (your.domain) — these fix CSRF/login issues behind TLS-terminating proxies and harden host-header handling.

Why Deploy readeck-railway 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 readeck-railway 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.