Self-host Gitness with Levelrail

Harness Open Source, a Git host with code review, pipelines and an artifact registry in one binary. Apache-2.0 licensed. Uses an embedded SQLite database on the data volume. The first user to register becomes the admin, then turn off sign-ups. Pipelines that run containers need Docker access, which this template does not grant.

  • Authorharness
  • LicenceApache-2.0
  • Memory384 MiB
  • Archarm64
  • Services1

How to self-host Gitness

  1. Pull the images

    One image is pulled on your server.

    Show images
    • harness/harness:3.3.0
  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

    2 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.

Gitness requirements

Memory
About 384 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
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Gitness. 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 Gitness docs page.

Deploy Gitness your way

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

Deploy Gitness from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain gitness=app.example.com.

levelrail-cli templates install gitness --name my-gitness

Deploy Gitness with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/gitness/install \
  -d '{
    "name": "my-gitness"
  }'

Gitness configuration

Gitness services

ServiceImagePortsVolumes
gitness harness/harness:3.3.0 3000 data -> /data

Gitness environment variables

VariableServiceValue
GITNESS_URL_BASE gitness Preset by the template
GITNESS_USER_SIGNUP_ENABLED gitness Preset by the template

Ports and volumes

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

Gitness FAQ

How much memory does Gitness need?

The catalog lists about 384 MiB of memory for Gitness.

Does Gitness run on arm64?

For Gitness, an arm64 image is published; amd64 is image published.

What licence is Gitness under?

Gitness is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Gitness need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Gitness use?

Gitness listens on port 3000 inside the stack.

Where does Gitness keep its data?

In a named volume: data mounted at /data.

Can I deploy Gitness 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 Gitness, 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 harness/harness:3.3.0 is what you deploy there.

levelrail-cli templates install gitness --name my-gitness