Self-host Stash with Levelrail
A self hosted organiser and player for your personal video library, with tags and scraping.
- Authorstashapp
- LicenceAGPL-3.0-only
- Memory1 GiB
- Services1
How to self-host Stash
-
Pull the images
One image is pulled on your server.
Show images
stashapp/stash:v0.32.0
-
Create the app
One service starts in a single Compose app, with 6 named volume mounts for your data, on port 9999.
-
Fill in the secrets
5 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.
After the first start
- Run the setup wizard on first visit and set a username and password.
Stash requirements
- Memory
- About 1 GiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9999
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) 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 Stash. 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 Stash docs page.
Deploy Stash your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Stash from the CLI
levelrail-cli templates deploy stash --name my-stash Deploy Stash with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/stash/deploy Stash configuration
Stash services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| stash | stashapp/stash:v0.32.0 | 9999 | config -> /root/.stashdata -> /datagenerated -> /generatedmetadata -> /metadatacache -> /cacheblobs -> /blobs |
Stash environment variables
| Variable | Service | Value |
|---|---|---|
| STASH_CACHE | stash | Preset by the template |
| STASH_GENERATED | stash | Preset by the template |
| STASH_METADATA | stash | Preset by the template |
| STASH_PORT | stash | Preset by the template |
| STASH_STASH | stash | Preset by the template |
Ports and volumes
- Ports
- 9999
- Volumes
- 6 named mounts: config -> /root/.stash, data -> /data, generated -> /generated, metadata -> /metadata, cache -> /cache, blobs -> /blobs
Stash FAQ
How much memory does Stash need?
The catalog lists about 1 GiB of memory for Stash.
Does Stash run on arm64?
For Stash, arm64 support is not confirmed; amd64 is unknown.
What licence is Stash under?
Stash is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Stash need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Stash use?
Stash listens on port 9999 inside the stack.
Where does Stash keep its data?
In named volumes: config mounted at /root/.stash, data mounted at /data, generated mounted at /generated and metadata mounted at /metadata.
Can I deploy Stash 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 Stash, 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 stashapp/stash:v0.32.0 is what you deploy there.