Deploy and Host Koodo Reader on Railway

About Hosting Koodo Reader on Railway

Koodo Reader runs as a single Docker service on Railway using the upstream GHCR image pinned by immutable digest. This gives one-click web access with optional built-in file sync API support.

Tech Stack

• Caddy (serves the web UI on port 80)
• Node.js HTTP server (optional data-source API)
• Docker image: ghcr.io/koodo-reader/koodo-reader

Why Deploy Koodo Reader on Railway

Railway provides fast container deployment, automatic HTTPS domains, and simple environment variable management, making Koodo Reader easy to launch and maintain.

Common Use Cases

• Personal cloud reading workspace in browser
• Cross-device reading with optional file sync endpoint
• Team/internal ebook access portal

Deployment Notes

Use PORT=80 so Railway routes traffic to the web UI. Keep ENABLE_HTTP_SERVER=false for the simplest setup; set it to true to enable the authenticated sync API on the internal container process. If enabling sync, set secure SERVER_USERNAME and SERVER_PASSWORD.

Dependencies for Koodo Reader on Railway

This template is a single-service deployment with no external database dependency.

Deployment Dependencies