Deploy Komga
Self-hosted comics, manga and ebook server with OPDS and Kobo sync
Just deployed
/data
Deploy and Host Komga on Railway
Komga is a free, open-source (MIT) media server for comics, manga, BDs, magazines and ebooks. It scans folders of CBZ, CBR, PDF and EPUB files, reads their metadata, and serves them through a web reader, a REST API, OPDS feeds, Kobo Sync and KOReader Sync, with multiple users and per-library access.
About Hosting Komga
This template runs Komga 1.30.1 from the official gotson/komga image, pinned by version and digest and built from a public GitHub repository, as one service with one volume at /data. Komga keeps its SQLite databases, search index and logs in /data/config, and your books in /data/library. On first boot the service claims itself for KOMGA_ADMIN_EMAIL with a generated KOMGA_ADMIN_PASSWORD (find it in the service's Variables tab), so nobody else can claim the public URL first, and it creates a library called "Library". After that, sign in, upload books to the volume with the Railway CLI (railway volume files upload ./My-Series /library/My-Series) and scan the library. Updates arrive as Railway update notices when the repository moves to a new Komga release.
Common Use Cases
- Read your own comic, manga and ebook collection in the browser on any device
- Sync books and reading progress to a Kobo e-reader or KOReader
- Share a library with family or friends, with separate accounts and age restrictions
Dependencies for Komga Hosting
- One Railway volume mounted at
/data(databases, search index and books) - No external database: Komga uses embedded SQLite
Deployment Dependencies
- Komga: https://komga.org
- Komga source and releases: https://github.com/gotson/komga/releases
- Template repository: https://github.com/aalfath/komga-railway-template
Implementation Details
Services: Komga (web UI, reader, OPDS and API on a public domain, health check /actuator/health). Variables: KOMGA_ADMIN_EMAIL (default admin@example.com, change it at deploy if you like), KOMGA_ADMIN_PASSWORD (generated) and PORT (25600). The first-boot setup only runs on a fresh volume, so later redeploys never reset accounts or libraries, and changing the password variable later does not change the account: change it in Komga under Account settings. Komga has no web upload; use railway volume files upload, where paths start at the volume root (/library/... lands in /data/library/...). Optional settings such as OAuth2 login, TZ or a larger JAVA_TOOL_OPTIONS heap (default -Xmx1g) can be added as variables or in /data/config/application.yml. Before applying an update notice, read the repository's CHANGELOG.md.
Why Deploy Komga 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 Komga 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.
Template Content
