Self-host Zipline with Levelrail
A self-hosted file and screenshot host with a share-first upload flow and its own URL shortener.
- Authordiced
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services2
How to self-host Zipline
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineghcr.io/diced/zipline:3.7.9
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 3 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.
Zipline requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- 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.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Zipline. 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 Zipline docs page.
Deploy Zipline your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Zipline from the CLI
levelrail-cli templates deploy zipline --name my-zipline Deploy Zipline with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/zipline/deploy Zipline configuration
Zipline services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | zipline_db_data -> /var/lib/postgresql/data |
| zipline | ghcr.io/diced/zipline:3.7.9 | 3000 | zipline_uploads -> /zipline/uploads |
Zipline environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| CORE_DATABASE_URL | zipline | Generated at deploy |
| CORE_RETURN_HTTPS | zipline | Preset by the template |
| CORE_SECRET | zipline | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: zipline_db_data -> /var/lib/postgresql/data, zipline_uploads -> /zipline/uploads
Zipline FAQ
How much memory does Zipline need?
The catalog lists about 256 MiB of memory for Zipline across its 2 services.
Does Zipline run on arm64?
For Zipline, an arm64 image is published; amd64 is image published.
What licence is Zipline under?
Zipline is licensed under MIT, which is permissive, with few conditions on reuse.
Does Zipline need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Zipline bundle?
The template includes Postgres, running as its own service.
Which ports does Zipline use?
Zipline listens on port 3000 inside the stack.
Where does Zipline keep its data?
In named volumes: zipline_db_data mounted at /var/lib/postgresql/data and zipline_uploads mounted at /zipline/uploads.
Can I deploy Zipline on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id zipline for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ghcr.io/diced/zipline:3.7.9 is what you deploy there.