Self-host Forgejo (Postgres) on a VPS
Forgejo backed by Postgres instead of its default SQLite, for a multi-writer-safe production setup.
levelrail-cli templates deploy forgejo-postgres --name my-forgejo-postgresSpecification
- Status
- Listed
- Category
- Developer Tools
- Services
- db, forgejo
- Ports
- 3000
- Volumes
- 2
- Memory
- about 512 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- not yet recorded
About Forgejo (Postgres)
Forgejo backed by Postgres instead of its default SQLite, for a multi-writer-safe production setup. Runs 2 containers (db, forgejo), with forgejo listening on port 3000; data is kept in named volumes.
What it deploys
Forgejo (Postgres) runs as 2 services in a single Compose app, listening on port 3000, with 2 named volume mounts.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| db | postgres | 16-alpine | none | forgejo_postgres_db_data -> /var/lib/postgresql/data |
| forgejo | codeberg.org/forgejo/forgejo | 9.0.3 | 3000 | forgejo_postgres_data -> /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 3000 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 |
|---|---|---|
| db | POSTGRES_DB | Preset by the template |
| db | POSTGRES_PASSWORD | Generated at deploy |
| db | POSTGRES_USER | Preset by the template |
| forgejo | FORGEJO__database__DB_TYPE | Preset by the template |
| forgejo | FORGEJO__database__HOST | Preset by the template |
| forgejo | FORGEJO__database__NAME | Preset by the template |
| forgejo | FORGEJO__database__PASSWD | Generated at deploy |
| forgejo | FORGEJO__database__USER | Preset by the template |
| forgejo | FORGEJO__security__SECRET_KEY | Generated at deploy |
| forgejo | FORGEJO__server__ROOT_URL | Preset by the template |
Install Forgejo (Postgres) 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 forgejo-postgres -
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 forgejo-postgres --name my-forgejo-postgres
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Forgejo (Postgres).
Docs and upstream
More in Developer Tools
- ForgejoA lightweight, community-governed Git forge with issues, pull requests, and CI runners.
- FliptA self-hosted feature flag and experimentation platform with a built-in UI and REST/gRPC APIs.
- GitBucketA Git hosting platform with issues, pull requests and a wiki, on a data volume. The first account is root with the password root, so change it right after the first sign in.
- GiteaA lightweight, self-hosted Git service with issues, pull requests, and a package registry.
- FlareSolverrA headless-browser proxy that solves Cloudflare and DDoS-Guard challenges for other self-hosted tools.
- Gitea (Postgres)Gitea backed by Postgres instead of its default MySQL, for operators standardizing on one database engine.