English
GitLab Hosting
GitLab is a self-hosted DevOps platform for Git repositories, merge requests, CI pipelines, issues, and a built-in container registry.
- One click deploy
- 100 GB Disk Space Needed
- 8 GB RAM Memory needed
- From 20 € Price
No setup fees
Official links
GitLab’s official links and original website
- More
GitLab Website
What you get
on AvaHost
One-click deployment, a custom domain, free HTTPS, automatic application updates, and scheduled backups come with every Cloud App. You can run multiple apps on one server, and terminal access is included.
This template does not include a database container.
Tech
- Docker image
- gitlab/gitlab-ce:latest
- Default port
- 0
How GitLab works
GitLab Community Edition in the Omnibus Docker image, gitlab/gitlab-ce, packs the web application, background jobs, and its own PostgreSQL into one container. You set an external URL to the hostname users will clone from and sign in on. The documented volumes hold config, logs, and data under /etc/gitlab, /var/log/gitlab, and /var/opt/gitlab. The image also publishes a git protocol port. This page sticks to HTTPS remotes, which the hostname and certificate already cover.
Current GitLab docs treat 16 GB as a single-node baseline and say a memory-constrained install can run with at least 8 GB. Plan 4 on AvaHost is 8 GB and 4 vCPU, which is the top plan an app page is allowed to recommend. Heavier user counts, large CI, or a busy registry need a conversation about a bigger VPS. This catalog does not list a plan above that ceiling. The bundled database is inside the GitLab image, so AvaHost does not add a second database container for this baseline.
Key GitLab features
Teams get repositories, merge requests, issues, and CI from the same sign-in. A container registry can be enabled with its own domain and storage, which GitLab documents separately. The registry is optional and is a disk consumer. Shared memory for the container is part of the Docker guide. Swap advice in the constrained-environment page is a host concern, not something this page promises to size for you.
AvaHost updates the deployment automatically and backs up the persistent volumes on a schedule. You should still read GitLab upgrade notes, because major versions have mandatory stop points. Repository data and artifacts are the bulk of the backup. Application mail is not included, so notification email needs a mail path you configure if you want it.
GitLab vs GitHub
GitLab
GitLab on AvaHost is the application running on your VPS, with the data in your volumes. GitHub is GitHub's hosted product, with its own runners, policies, and pricing. Choose GitHub when you want that operated service. Choose this package when the requirement is a self-hosted GitLab CE and you can meet the memory floor.
GitHub
Feature checklists drift between versions. Compare the CE features you need against the current GitLab docs rather than against a frozen list.
Who uses GitLab
Software teams that cannot put source on a public hosted forge use GitLab. So do groups who want CI next to the git data. It is a poor fit for a tiny brochure site, and it is a poor fit for a 1 GB plan. If the docs' 16 GB baseline is your real workload, say so before you order, because Plan 4 is the 8 GB constrained floor, not a large reference architecture.
Self-hosting GitLab: requirements and cost
This baseline is 8192 MB of RAM and 2 CPU cores, image gitlab/gitlab-ce, PostgreSQL inside the Omnibus image rather than a separate container. Repositories and registry blobs outgrow the install itself. 100 GB on Plan 4 is the disk that comes with this recommendation, and growth past that is a hosting conversation once history and artifacts pile up. On AvaHost the recommended minimum for GitLab is Plan 4 at €20. The GitLab package includes one-click deployment, your hostname, automated HTTPS, automatic updates, and scheduled backups. Git over HTTPS uses that hostname. Application mail is not included with GitLab.
F.A.Q
GitLab on AvaHost is listed from €20 on Plan 4. GitLab’s own docs ask for at least 8 GB in a constrained single-node install and describe 16 GB as a fuller baseline. Plan 4 is 8 GB, which is the top plan this catalog shows on an app page. Busy CI, many users, or a large registry can need more than that ceiling.
Yes. The external URL should be a hostname you control, with automated HTTPS on the web UI and on HTTPS git remotes. DNS has to match that name or clones and sign-in fail. You manage the zone, the user accounts inside GitLab, and whether the registry domain is enabled.
AvaHost applies GitLab updates automatically and keeps the Omnibus volumes attached, with backups on a schedule. Read the version’s upgrade notes anyway, because GitLab documents required paths between major releases. After an update, check sign-in, a clone over HTTPS, and one pipeline. Keep registry storage in mind when you estimate backup size.
Repositories, CI artifacts, and an enabled container registry. The 100 GB included with Plan 4 is a starting point, not a cap on how large history can grow. Plan the next disk increase before the volume fills. The bundled PostgreSQL lives inside the same data volume, so it is part of that backup story.