Self-host Picsur with Levelrail
A simple image host with on-the-fly format conversion.
- AuthorCaramelFur
- LicenceAGPL-3.0
- Memory512 MiB
- Services2
How to self-host Picsur
-
Pull the images
2 images are pulled on your server.
Show images
postgres:17-alpineghcr.io/caramelfur/picsur:0.5.6
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 6 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.
Picsur requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, 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 Picsur. 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 Picsur docs page.
Deploy Picsur your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Picsur from the CLI
levelrail-cli templates deploy picsur --name my-picsur Deploy Picsur with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/picsur/deploy Picsur configuration
Picsur services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:17-alpine | none | db_data -> /var/lib/postgresql/data |
| picsur | ghcr.io/caramelfur/picsur:0.5.6 | 8080 | none |
Picsur 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 |
| PICSUR_ADMIN_PASSWORD | picsur | Generated at deploy |
| PICSUR_DB_DATABASE | picsur | Preset by the template |
| PICSUR_DB_HOST | picsur | Preset by the template |
| PICSUR_DB_PASSWORD | picsur | Generated at deploy |
| PICSUR_DB_PORT | picsur | Preset by the template |
Show all 10 variables
- PICSUR_DB_USERNAMEpicsurPreset by the template
- PICSUR_JWT_SECRETpicsurGenerated at deploy
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: db_data -> /var/lib/postgresql/data
Picsur FAQ
How much memory does Picsur need?
The catalog lists about 512 MiB of memory for Picsur across its 2 services.
Does Picsur run on arm64?
For Picsur, arm64 support is not confirmed; amd64 is unknown.
What licence is Picsur under?
Picsur is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Picsur need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Picsur bundle?
The template includes Postgres, running as its own service.
Which ports does Picsur use?
Picsur listens on port 8080 inside the stack.
Where does Picsur keep its data?
In a named volume: db_data mounted at /var/lib/postgresql/data.
Can I deploy Picsur 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 picsur for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:17-alpine, ghcr.io/caramelfur/picsur:0.5.6 is what you deploy there.