Self-host PG Back Web with Levelrail
A web UI for scheduling, encrypting, and restoring PostgreSQL backups.
- Authoreduardolat
- LicenceAGPL-3.0
- Memory256 MiB
- Archarm64
- Services2
How to self-host PG Back Web
-
Pull the images
2 images are pulled on your server.
Show images
eduardolat/pgbackweb:0.5.2postgres:17-alpine
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8085.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 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.
PG Back Web requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8085
- 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 8085 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 PG Back Web. 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 PG Back Web docs page.
Deploy PG Back Web your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy PG Back Web from the CLI
levelrail-cli templates deploy pgbackweb --name my-pgbackweb Deploy PG Back Web with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/pgbackweb/deploy PG Back Web configuration
PG Back Web services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| pgbackweb | eduardolat/pgbackweb:0.5.2 | 8085 | pgbackweb_data -> /backups |
| pgbackweb-db | postgres:17-alpine | none | pgbackweb_postgres_data -> /var/lib/postgresql/data |
PG Back Web environment variables
| Variable | Service | Value |
|---|---|---|
| PBW_ENCRYPTION_KEY | pgbackweb | Generated at deploy |
| PBW_POSTGRES_CONN_STRING | pgbackweb | Generated at deploy |
| POSTGRES_DB | pgbackweb-db | Preset by the template |
| POSTGRES_PASSWORD | pgbackweb-db | Generated at deploy |
| POSTGRES_USER | pgbackweb-db | Preset by the template |
Ports and volumes
- Ports
- 8085
- Volumes
- 2 named mounts: pgbackweb_data -> /backups, pgbackweb_postgres_data -> /var/lib/postgresql/data
PG Back Web FAQ
How much memory does PG Back Web need?
The catalog lists about 256 MiB of memory for PG Back Web across its 2 services.
Does PG Back Web run on arm64?
For PG Back Web, an arm64 image is published; amd64 is image published.
What licence is PG Back Web under?
PG Back Web is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does PG Back Web need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does PG Back Web bundle?
The template includes Postgres, running as its own service.
Which ports does PG Back Web use?
PG Back Web listens on port 8085 inside the stack.
Where does PG Back Web keep its data?
In named volumes: pgbackweb_data mounted at /backups and pgbackweb_postgres_data mounted at /var/lib/postgresql/data.
Can I deploy PG Back Web 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 PG Back Web, 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 eduardolat/pgbackweb:0.5.2, postgres:17-alpine is what you deploy there.