FAQ
A list of frequently asked questions about Stump:
Demo
The demo is currently unavailable. I will try to get it back up as soon as possible. See the relevant issue.
A demo can be found at demo.stumpapp.dev. The login credentials are:
- Username:
demouser - Password:
demouser10801
What is Stump?
Stump is an open source, self hostable, media server for digital books (ebooks, comic books, manga, etc). It is designed to be easy to use and easy to deploy.
The short on how it works:
- Install and run Stump on a computer or NAS (Network Attached Storage).
- Configure your libraries
- Read your media using the web interface or any compatible client
Stump is not a tool used for fetching or downloading any kind of media. It is a tool used to host and access your own media. Think of it like a personal Netflix for comic books/manga/etc that lives on a computer in your home.
Motivations
There are some really solid, self-hostable, OPDS media servers out there. I started out using Komga. I initially started developing Stump because I thought it would be cool to learn what goes into making something like Komga myself.
In general, Stump strives for the following:
- Small footprint and low resource usage
- Efficiency and performance, even on less powerful hardware (e.g., Raspberry Pi)
- Intuitive, pretty, and easy to use interface
- Wide format support (e.g., PDF, EPUB, CBZ/CBR)
Compatibility
Stump should work on all major browsers and operating systems.
Generally speaking, 1GB of RAM and disk space is enough. Stump also runs well on low-powered ARM-based single board computers, such as a Raspberry Pi.
Roadmap
The following items are long-term goals for Stump:
- Story arcs and other book-relating concepts
- In-app metadata fetching and editing
- File watching
- More book analysis tools and statistics (I like charts)
- Bulk management
- Declarative library patterns
- Book club features
- Dedicated mobile and desktop apps
- Optional SSO / OAuth
- Audiobooks + alternate book versions
Some of these long-term items have been started, some haven’t. Take a look at the GitHub Projects to see what is currently being worked on and what is planned for the future.
If you’re interested in tracking the broader development of individual or otherwise isolated features, you can take a look at GitHub issues.