Self-host Forgejo (Postgres) with Levelrail

Forgejo backed by Postgres instead of its default SQLite, for a multi-writer-safe production setup.

  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Forgejo (Postgres)

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • codeberg.org/forgejo/forgejo:9.0.3
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Forgejo (Postgres) requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 3000 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 Forgejo (Postgres). 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 Forgejo (Postgres) docs page.

Deploy Forgejo (Postgres) your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Forgejo (Postgres) from the CLI

levelrail-cli templates deploy forgejo-postgres --name my-forgejo-postgres

Deploy Forgejo (Postgres) with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/forgejo-postgres/deploy

Forgejo (Postgres) configuration

Forgejo (Postgres) services

ServiceImagePortsVolumes
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

Forgejo (Postgres) environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
FORGEJO__database__DB_TYPE forgejo Preset by the template
FORGEJO__database__HOST forgejo Preset by the template
FORGEJO__database__NAME forgejo Preset by the template
FORGEJO__database__PASSWD forgejo Generated at deploy
FORGEJO__database__USER forgejo Preset by the template
Show all 10 variables
  • FORGEJO__security__SECRET_KEYforgejoGenerated at deploy
  • FORGEJO__server__ROOT_URLforgejoPreset by the template

Ports and volumes

Ports
3000
Volumes
2 named mounts: forgejo_postgres_db_data -> /var/lib/postgresql/data, forgejo_postgres_data -> /data

Forgejo (Postgres) FAQ

How much memory does Forgejo (Postgres) need?

The catalog lists about 512 MiB of memory for Forgejo (Postgres) across its 2 services.

Does Forgejo (Postgres) run on arm64?

For Forgejo (Postgres), an arm64 image is published; amd64 is image published.

Does Forgejo (Postgres) need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Forgejo (Postgres) bundle?

The template includes Postgres, running as its own service.

Which ports does Forgejo (Postgres) use?

Forgejo (Postgres) listens on port 3000 inside the stack.

Where does Forgejo (Postgres) keep its data?

In named volumes: forgejo_postgres_db_data mounted at /var/lib/postgresql/data and forgejo_postgres_data mounted at /data.

Can I deploy Forgejo (Postgres) 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 Forgejo (Postgres), 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 postgres:16-alpine, codeberg.org/forgejo/forgejo:9.0.3 is what you deploy there.

levelrail-cli templates deploy forgejo-postgres --name my-forgejo-postgres