Self-host GitLab on a VPS
GitLab Community Edition: Git hosting, CI/CD, issues, and a container registry in one Omnibus image.
levelrail-cli templates deploy gitlab --name my-gitlabSpecification
- Status
- Listed
- Category
- Developer Tools
- Services
- gitlab
- Ports
- 80, 22
- Volumes
- 3
- Memory
- about 4 GiB
- arm64
- not available
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, MIT
About GitLab
GitLab Community Edition: Git hosting, CI/CD, issues, and a container registry in one Omnibus image. Runs as a single container from the gitlab-ce image, listening on port 80; data is kept in named volumes.
What it deploys
GitLab runs as one service in a single Compose app, listening on ports 80, 22, with 3 named volume mounts.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| gitlab | gitlab/gitlab-ce | 17.5.2-ce.0 | 80, 22 | gitlab_config -> /etc/gitlabgitlab_logs -> /var/log/gitlabgitlab_data -> /var/opt/gitlab |
Before you install
- CPU architecture. amd64 only. At least one image lists no linux/arm64, so there is no native Arm image.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
- Host ports. It publishes ports 80, 22 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| gitlab | GITLAB_OMNIBUS_CONFIG | Preset by the template |
| gitlab | GITLAB_ROOT_PASSWORD | Generated at deploy |
Install GitLab on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get gitlab -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy gitlab --name my-gitlab
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then GitLab.
Docs and upstream
More in Developer Tools
- Gitea (Postgres)Gitea backed by Postgres instead of its default MySQL, for operators standardizing on one database engine.
- GitLab CEA complete DevOps platform for source control, code review, issues, and CI/CD in one place.
- GiteaA lightweight, self-hosted Git service with issues, pull requests, and a package registry.
- GitnessHarness 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.
- GitBucketA Git hosting platform with issues, pull requests and a wiki, on a data volume. The first account is root with the password root, so change it right after the first sign in.
- GoCDA continuous delivery server with pipeline visualisation, running on a data volume. Needs about 1 GB of memory. Authentication is off until you set it up, so restrict access first.