4.3 KiB
| comments | description |
|---|---|
| false | Read through the GitLab installation methods. |
Installation
GitLab can be installed in most GNU/Linux distributions and in a number of cloud providers. To get the best experience from GitLab you need to balance:
- Performance
- Reliability
- Ease of administration (backups, upgrades and troubleshooting)
- Cost of hosting
TIP: If in doubt, choose Omnibus: Our Omnibus GitLab packages are mature, scalable, support high availability and are used today on GitLab.com. Our Helm charts are recommended for those who are familiar with Kubernetes.
Requirements
Before installing GitLab, make sure to check the requirements documentation which includes useful information on the supported Operating Systems as well as the hardware requirements.
Install GitLab using the Omnibus GitLab package (recommended)
This installation method uses the Omnibus GitLab package, using our official deb/rpm repositories. This is the recommended way.
If you need additional flexibility and resilience, we recommend deploying GitLab as described in our High Availability documentation.
> Install GitLab using the Omnibus GitLab package.
Alternative to Omnibus GitLab
If the GitLab Omnibus package is not available in your distribution, you can choose between:
- Installing GitLab from source: Useful for unsupported systems like *BSD. For an overview of the directory structure, read the structure documentation. While the recommended database is PostgreSQL, we provide information to install GitLab using MySQL.
- Installing Omnibus GitLab using Docker.
Install GitLab on Kubernetes via the GitLab Helm charts
NOTE: Kubernetes experience required: We recommend being familiar with Kubernetes before using it to deploy GitLab in production. The methods for management, observability, and some concepts are different than traditional deployments.
When installing GitLab on kubernetes, there are a number of trade-offs that you need to be aware of that may not be immediately obvious and could prevent you getting the best experience from GitLab:
- Configuration of features such as object storage and backups can be more challenging.
- Administration and troubleshooting requires Kubernetes knowledge.
- It can be more expensive for smaller installations. The default installation requires more resources than a single node Omnibus deployment, as most services are deployed in a redundant fashion.
- There are some feature limitations to be aware of.
> Install GitLab on Kubernetes using the GitLab Helm charts.
Install GitLab on cloud providers
GitLab can be installed on a variety of cloud providers:
- Install on AWS: Install GitLab on AWS using the community AMIs that GitLab provides.
- Install GitLab on Google Cloud Platform
- Install GitLab on Azure
- Install GitLab on OpenShift
- Install GitLab on DC/OS via GitLab-Mesosphere integration
- Install GitLab on Google Kubernetes Engine (GKE): video tutorial on the full process of installing GitLab on Google Kubernetes Engine (GKE), pushing an application to GitLab, building the app with GitLab CI/CD, and deploying to production.
- Getting started with GitLab and DigitalOcean: requirements, installation process, updates.
- Demo: Cloud Native Development with GitLab: video demonstration on how to install GitLab on Kubernetes, build a project, create Review Apps, store Docker images in Container Registry, deploy to production on Kubernetes, and monitor with Prometheus.
- Testing only! DigitalOcean and Docker Machine: Quickly test any version of GitLab on DigitalOcean using Docker Machine.