Self-host Gitea (Postgres) with Levelrail

Gitea backed by Postgres instead of its default MySQL, for operators standardizing on one database engine.

  • Authorgo-gitea
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Gitea (Postgres)

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • gitea/gitea:1.23.1
  2. Create the app

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

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, 6 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.

Gitea (Postgres) requirements

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

Deploy Gitea (Postgres) your way

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

Deploy Gitea (Postgres) from the CLI

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

Deploy Gitea (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/gitea-postgres/deploy

Gitea (Postgres) configuration

Gitea (Postgres) services

ServiceImagePortsVolumes
db postgres:16-alpine none gitea_postgres_db_data -> /var/lib/postgresql/data
gitea gitea/gitea:1.23.1 3000, 22 gitea_postgres_data -> /data

Gitea (Postgres) environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
GITEA__database__DB_TYPE gitea Preset by the template
GITEA__database__HOST gitea Preset by the template
GITEA__database__NAME gitea Preset by the template
GITEA__database__PASSWD gitea Generated at deploy
GITEA__database__USER gitea Preset by the template

Ports and volumes

Ports
3000, 22
Volumes
2 named mounts: gitea_postgres_db_data -> /var/lib/postgresql/data, gitea_postgres_data -> /data

Gitea (Postgres) FAQ

How much memory does Gitea (Postgres) need?

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

Does Gitea (Postgres) run on arm64?

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

What licence is Gitea (Postgres) under?

Gitea (Postgres) is licensed under MIT, which is permissive, with few conditions on reuse.

Does Gitea (Postgres) need configuration before it starts?

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

Which database does Gitea (Postgres) bundle?

The template includes Postgres, running as its own service.

Which ports does Gitea (Postgres) use?

Gitea (Postgres) listens on ports 3000 and 22 inside the stack.

Where does Gitea (Postgres) keep its data?

In named volumes: gitea_postgres_db_data mounted at /var/lib/postgresql/data and gitea_postgres_data mounted at /data.

Can I deploy Gitea (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 has an entry with the id gitea-postgres for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, gitea/gitea:1.23.1 is what you deploy there.

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