Self-host Gitea with Levelrail

Verified

A lightweight, self-hosted Git service with issues, pull requests, and a package registry.

  • Authorgo-giteaVerified by Levelrail
  • LicenceMIT
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host Gitea

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • mariadb:11
    • 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

    3 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 requirements

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

Deploy Gitea your way

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

Deploy Gitea from the CLI

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

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

Gitea configuration

Gitea services

ServiceImagePortsVolumes
db mariadb:11 none gitea_db_data -> /var/lib/mysql
gitea gitea/gitea:1.23.1 3000, 22 gitea_data -> /data

Gitea environment variables

VariableServiceValue
MYSQL_DATABASE db Preset by the template
MYSQL_PASSWORD db Generated at deploy
MYSQL_ROOT_PASSWORD db Generated at deploy
MYSQL_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
Show all 9 variables
  • GITEA__database__USERgiteaPreset by the template

Ports and volumes

Ports
3000, 22
Volumes
2 named mounts: gitea_db_data -> /var/lib/mysql, gitea_data -> /data

Gitea FAQ

How much memory does Gitea need?

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

Does Gitea run on arm64?

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

What licence is Gitea under?

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

Does Gitea need configuration before it starts?

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

Which database does Gitea bundle?

The template includes MySQL, running as its own service.

Which ports does Gitea use?

Gitea listens on ports 3000 and 22 inside the stack.

Where does Gitea keep its data?

In named volumes: gitea_db_data mounted at /var/lib/mysql and gitea_data mounted at /data.

Can I deploy Gitea 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 Gitea, 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 mariadb:11, gitea/gitea:1.23.1 is what you deploy there.

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