Docker Install
Run FolioSpace Library on your own NAS or Docker host.
FolioSpace Library is self-hosted. Mount your local folders into the container, create an access key on first run, then index the container paths shown in the setup page.
Pull the image
docker pull funland/foliospace-library:1.01
The current Docker Hub tag is funland/foliospace-library:1.01.
Release 1.01 is published for linux/amd64 and
linux/arm64. The latest tag also points to
the current public release.
FolioSpace Library 1.01
Release 1.01 adds audited MAME content-equivalence support across compatible runtime updates while keeping library data and policy under the user's control.
- Reviewed MAME content definitions cover compatible 0.287, 0.288, and 0.289 sets.
- Changed definitions and incomplete ROM, BIOS, or dependency closures still require a fresh audit.
- Existing Reader, SpatialEMU, video, Client API, and MCP workflows remain available.
Run with mounted libraries
docker run -d \
--name foliospace-library \
--restart unless-stopped \
-p 8080:8080 \
-v /volume1/docker/foliospace-library/config:/config \
-v /volume2/ComicCenter:/library:ro \
-v /volume2/Books:/books:ro \
-v /volume2/GameROMS:/games:ro \
-v /volume2/MovieCollection/Movies:/videos:ro \
-e FOLIOSPACE_DIRECTORY_ROOTS=/library,/books,/games,/videos \
funland/foliospace-library:1.01
Open http://localhost:8080 or your NAS address. The setup
page creates the first access key and library.
The /config mount must be a persistent writable directory.
FolioSpace Library stores SQLite data, generated covers, thumbnails,
and cache files there. The current image also attempts to repair common
bind-mount ownership issues during startup.
Docker Compose
Use the same 1.01 image in your Compose file. Keep
/config writable and persistent, and mount content folders
read-only whenever possible.
services:
foliospace-library:
image: funland/foliospace-library:1.01
restart: unless-stopped
ports:
- "8080:8080"
volumes:
- ./data/config:/config
- /path/to/books:/books:ro
environment:
FOLIOSPACE_DIRECTORY_ROOTS: /books
Replace /path/to/books with a host path on your machine.
The selected library path in the Web UI is the container-visible
path, /books in this example.
Important path rule
The path selected in the web UI is the path inside the container. If a
NAS folder does not appear in the setup picker, add a Docker volume
mapping first and include the container path in
FOLIOSPACE_DIRECTORY_ROOTS. Video folders work the same
way: mount the host path and select the container-visible path such as
/videos.
Keep content mounts read-only when possible. FolioSpace Library indexes user-owned local files and does not provide cloud hosting, ROM downloads, or built-in copyrighted resources.