Self-host Forgejo with Levelrail

Verified

A lightweight, community-governed Git forge with issues, pull requests, and CI runners.

  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host Forgejo

  1. Pull the images

    One image is pulled on your server.

    Show images
    • codeberg.org/forgejo/forgejo:9.0.3
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 3000.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 1 setting is 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 requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 tested
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Verified. Verified on arm64 with image tag 9.0.3. Our CI ran this exact image version and it answered on its health path. Evidence
  • 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. 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 docs page.

Deploy Forgejo your way

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

Deploy Forgejo from the CLI

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

Deploy Forgejo 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/deploy

Forgejo configuration

Forgejo services

ServiceImagePortsVolumes
forgejo codeberg.org/forgejo/forgejo:9.0.3 3000 forgejo_data -> /data

Forgejo environment variables

VariableServiceValue
FORGEJO__security__SECRET_KEY forgejo Generated at deploy
FORGEJO__server__ROOT_URL forgejo Preset by the template

Ports and volumes

Ports
3000
Volumes
1 named mount: forgejo_data -> /data

Forgejo FAQ

How much memory does Forgejo need?

The catalog lists about 512 MiB of memory for Forgejo.

Does Forgejo run on arm64?

For Forgejo, arm64 is tested; amd64 is image published.

Does Forgejo need configuration before it starts?

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

Which ports does Forgejo use?

Forgejo listens on port 3000 inside the stack.

Where does Forgejo keep its data?

In a named volume: forgejo_data mounted at /data.

Can I deploy Forgejo 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 forgejo for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image codeberg.org/forgejo/forgejo:9.0.3 is what you deploy there.

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