Deploy and Host Grimmory on Railway

Grimmory is a community-maintained fork of BookLore for self-hosting your digital book and audiobook library. It keeps the familiar BookLore-style experience for managing EPUBs, PDFs, and audiobooks, with metadata fetching, cover handling, reading progress, and a modern web UI.

About Hosting Grimmory

Grimmory runs as a Java application server backed by MariaDB. This template handles the full setup: the Grimmory app, a MariaDB database, and persistent volume storage for your book files and app data. Railway's single-volume-per-service limitation is handled with bind mounts, so your books and configuration persist across redeploys. Once deployed, create an account, point your library at /books, and start uploading.

Common Use Cases

Managing a personal digital book and audiobook collection with automatic metadata fetching
Self-hosting a BookLore-compatible library manager with an actively maintained community fork
Organising and tracking reading progress across multiple devices

Dependencies for Grimmory Hosting

MariaDB (included in template)
Persistent volume storage (included in template)

Deployment Dependencies

Implementation Details

This template uses a custom Dockerfile that wraps the official grimmory/grimmory Docker image. A runtime entrypoint script maps subdirectories from a single Railway volume (/booklore-data) to the paths Grimmory expects (/app/data and /books) using bind mounts.

Why Deploy Grimmory on Railway?

Railway handles the infrastructure so you can focus on your library. With one click, you get a fully configured Grimmory instance with MariaDB and persistent storage - no Docker Compose, no server management, no manual database setup.