kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/install
History
Marcel Amirault 513d3f5811 Fix markdown in various docs 
Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc
2019-08-30 02:25:44 +00:00
..
aws Change gitlab-rake to gitlab-backup for backup and restore tasks 2019-08-07 09:14:52 +10:00
azure Fix markdown in various docs 2019-08-30 02:25:44 +00:00
google_cloud_platform
kubernetes
openshift_and_gitlab
pivotal
digitaloceandocker.md
docker.md Fix assorted links 2019-08-07 06:19:00 +00:00
google-protobuf.md
installation.md Merge branch 'nelbacha-master-patch-08542' into 'master' 2019-08-28 16:39:42 +00:00
ldap.md
README.md Update capitalization in /dev docs 2019-08-27 08:44:07 +00:00
redis.md
relative_url.md Update capitalization in /dev docs 2019-08-27 08:44:07 +00:00
requirements.md Make ruby 2.6 the officially supported version 2019-08-14 23:16:55 +00:00
structure.md

README.md

comments description type
false Read through the GitLab installation methods. index

Installation (CORE ONLY)

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), and cost of hosting.

There are many ways you can install GitLab depending on your platform:

  1. Omnibus GitLab: The official deb/rpm packages that contain a bundle of GitLab and the various components it depends on like PostgreSQL, Redis, Sidekiq, etc.
  2. GitLab Helm chart: The cloud native Helm chart for installing GitLab and all its components on Kubernetes.
  3. Docker: The Omnibus GitLab packages dockerized.
  4. Source: Install GitLab and all its components from scratch.

TIP: If in doubt, choose Omnibus: The Omnibus GitLab packages are mature, scalable, support high availability and are used today on GitLab.com. The 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.

Installing GitLab using the Omnibus GitLab package (recommended)

The Omnibus GitLab package uses our official deb/rpm repositories. This is recommended for most users.

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.

Installing 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 some trade-offs that you need to be aware of:

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

Installing GitLab with Docker

GitLab maintains a set of official Docker images based on the Omnibus GitLab package.

> Install GitLab using the official GitLab Docker images.

Installing GitLab from source

If the GitLab Omnibus package is not available in your distribution, you can install GitLab from source: Useful for unsupported systems like *BSD. For an overview of the directory structure, read the structure documentation.

> Install GitLab from source.

Installing GitLab on cloud providers

GitLab can be installed on a variety of cloud providers by using any of the above methods, provided the cloud provider supports it.