Self-host Spoolman with Levelrail
A filament spool inventory manager for 3D printers with usage tracking and printer firmware integrations. MIT licensed. On first open, add your filaments and vendors; there is no login, so keep it behind a private network or an auth proxy.
- AuthorDonkie
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host Spoolman
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/donkie/spoolman:0.27.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Spoolman requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Spoolman. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Spoolman docs page.
Deploy Spoolman your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Spoolman from the CLI
levelrail-cli templates install spoolman --name my-spoolman Deploy Spoolman with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/spoolman/install \
-d '{
"name": "my-spoolman"
}' Spoolman configuration
Spoolman services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| spoolman | ghcr.io/donkie/spoolman:0.27.1 | 8000 | data -> /home/app/.local/share/spoolman |
Spoolman environment variables
| Variable | Service | Value |
|---|---|---|
| SPOOLMAN_DB_TYPE | spoolman | Preset by the template |
| TZ | spoolman | Preset by the template |
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: data -> /home/app/.local/share/spoolman
Spoolman FAQ
How much memory does Spoolman need?
The catalog lists about 256 MiB of memory for Spoolman.
Does Spoolman run on arm64?
For Spoolman, an arm64 image is published; amd64 is image published.
What licence is Spoolman under?
Spoolman is licensed under MIT, which is permissive, with few conditions on reuse.
Does Spoolman need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Spoolman use?
Spoolman listens on port 8000 inside the stack.
Where does Spoolman keep its data?
In a named volume: data mounted at /home/app/.local/share/spoolman.
Can I deploy Spoolman on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Spoolman, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/donkie/spoolman:0.27.1 is what you deploy there.