Self-host PG Back Web on a VPS
A web UI for scheduling, encrypting, and restoring PostgreSQL backups.
levelrail-cli templates deploy pgbackweb --name my-pgbackwebSpecification
- Status
- Listed
- Category
- Database Tools
- Services
- pgbackweb, pgbackweb-db
- Ports
- 8085
- Volumes
- 2
- Memory
- about 256 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
About PG Back Web
A web UI for scheduling, encrypting, and restoring PostgreSQL backups. Runs 2 containers (pgbackweb, pgbackweb-db), with pgbackweb listening on port 8085; data is kept in named volumes.
What it deploys
PG Back Web runs as 2 services in a single Compose app, listening on port 8085, with 2 named volume mounts.
| Service | Image | Tag | 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 |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8085 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 3 secrets are generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| pgbackweb | PBW_ENCRYPTION_KEY | Generated at deploy |
| pgbackweb | PBW_POSTGRES_CONN_STRING | Generated at deploy |
| pgbackweb-db | POSTGRES_DB | Preset by the template |
| pgbackweb-db | POSTGRES_PASSWORD | Generated at deploy |
| pgbackweb-db | POSTGRES_USER | Preset by the template |
Install PG Back Web on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get pgbackweb -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy pgbackweb --name my-pgbackweb
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then PG Back Web.
Docs and upstream
More in Database Tools
- pgAdminA full-featured web GUI for administering and querying PostgreSQL databases.
- pgvector PostgresPostgreSQL 17 with the pgvector extension preinstalled, for embeddings next to your relational data.
- phpMyAdminA web-based admin tool for MySQL and MariaDB, built for ad-hoc use against any reachable database.
- OrientDBA multi model database for graphs and documents with the Studio web console, a generated root password and data volumes. The binary protocol port 2424 stays private.
- OpenSearchA single node OpenSearch search and analytics engine with the security plugin on, a persistent volume, a generated admin password and a 512 MB Java heap. The API speaks HTTPS with a self signed certificate and is not published on the host, so reach it from other services in this project at opensearch:9200.
- PostgreSQLThe PostgreSQL relational database server on the official Alpine image, with a persistent volume and a generated password. It is not published on the host, so reach it from other services in this project at postgres:5432.