Deploy BookLore
Self-hosted multi-user ebook, PDF and comic library, with MariaDB
Just deployed
/data
Just deployed
/var/lib/mysql
Deploy and Host BookLore on Railway
BookLore is a self-hosted, multi-user digital library for your books. It organises EPUB, PDF, comic and audiobook files into libraries and smart shelves, fetches covers and metadata automatically, and has a built-in browser reader, Kobo and KOReader sync, OPDS for reading apps, and BookDrop imports. It is open source (AGPL-3.0).
About Hosting BookLore
BookLore is a Java (Spring Boot) web app that needs a MariaDB database and a disk for its settings, covers and book files. This template deploys two services built from one GitHub repo: BookLore v2.4.0 and MariaDB 11.4 LTS, both pinned by version and digest and each on its own volume. They talk over Railway's private network, the database password is generated at deploy, and BookLore waits for the database on its first boot. Nothing has to be filled in. After the deploy, open the public URL and create the admin account in the setup wizard straight away, then add a library that uses the /data/books folder.
Common Use Cases
- Keep a private ebook, PDF and comic collection in one place and read it in any browser
- Share a family or book-club library, with separate shelves and reading progress for each user
- Sync books and reading progress to a Kobo, KOReader or any OPDS reading app
Dependencies for BookLore Hosting
- MariaDB (included, 11.4 LTS on a volume)
- A Railway volume for BookLore's settings, covers and book files (included)
Deployment Dependencies
- BookLore source and releases: https://github.com/booklore-app/booklore/releases
- BookLore documentation: https://booklore.org/docs/getting-started
- Template repo (Dockerfiles, start script, changelog): https://github.com/aalfath/booklore-railway-template
Implementation Details
Services:
- BookLore: the web app and API, public on port 6060, health check
/api/v1/healthcheck. Its volume at/dataholdsapp(settings, covers, cache),books(your library folder) andbookdrop(files put here are queued for import). - MariaDB: BookLore's database (users, libraries, shelves, metadata, reading progress). Private network only, volume at
/var/lib/mysql.
After deploy:
- Open the BookLore URL and create the admin account. Only the first visitor can do this, so do it right away.
- Create a library with the folder
/data/books, then upload books in the UI or through BookDrop. - Optional: set up OIDC login, email (send to Kindle) and metadata sources in BookLore's settings. Add
TZorALLOWED_ORIGINSto the BookLore service if you need them.
Updates: both services build from the template repo. When we bump the pinned versions, Railway shows you an "update available" notice and you choose when to apply it. Read the repo's CHANGELOG.md first. Note: upstream has announced that BookLore is in maintenance mode (bug fixes and security updates), with BookOrbit as its successor.
Why Deploy BookLore 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 BookLore 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
