Self-host Vert with Levelrail
A fast file converter for images, video, audio, and documents, processed entirely without a third-party upload.
- AuthorVERT-sh
- LicenceAGPL-3.0
- Memory128 MiB
- Archarm64
- Services1
How to self-host Vert
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/vert-sh/vert:latest
-
Create the app
One service starts in a single Compose app, on port 80.
-
Fill in the secrets
4 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.
Vert requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- 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.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (ghcr.io/vert-sh/vert:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Vert. 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 Vert docs page.
Deploy Vert your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Vert from the CLI
levelrail-cli templates deploy vert --name my-vert Deploy Vert with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/vert/deploy Vert configuration
Vert services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| vert | ghcr.io/vert-sh/vert:latest | 80 | none |
Vert environment variables
| Variable | Service | Value |
|---|---|---|
| PUB_ENV | vert | Preset by the template |
| PUB_HOSTNAME | vert | Preset by the template |
| PUB_PORT | vert | Preset by the template |
| PUB_VERT_URL | vert | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- none
Vert FAQ
How much memory does Vert need?
The catalog lists about 128 MiB of memory for Vert.
Does Vert run on arm64?
For Vert, an arm64 image is published; amd64 is image published.
What licence is Vert under?
Vert is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Vert need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Vert use?
Vert listens on port 80 inside the stack.
Can I deploy Vert 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 Vert, 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/vert-sh/vert:latest is what you deploy there.