- Package Version
- Checking the versions of bundled software
- Signatures of GitLab, Inc. provided packages
- Checking for newer configuration options on upgrade
- Init system detection
The Linux package is bundled with all dependencies required for GitLab to function correctly. More details can be found at bundling dependencies document.
The released package versions are in the format
|The GitLab version this corresponds to.|
|The edition of GitLab this corresponds to.|
|The Linux package release. Usually, this is |
The Linux package requires various configuration to get the components in working order. If the configuration is not provided, the package uses the default values assumed in the package.
These defaults are noted in the package defaults document.
After the Linux package is installed, you can find the version of
GitLab and all bundled libraries in
Documentation on package signatures can be found at Signed Packages
/etc/gitlab/gitlab.rb configuration file is created when the Linux package is initially installed.
To avoid accidental overwrites of user configuration, the
/etc/gitlab/gitlab.rb configuration file is not updated
with new configuration when the Linux package installation is upgraded.
New configuration options are noted in the
The Linux package also provides a convenience command which compares the existing user configuration with the latest version of the template contained in the package.
To view a diff between your configuration file and the latest version, run:
sudo gitlab-ctl diff-config
/etc/gitlab/gitlab.rbconfiguration file, omit any leading
-characters on each line.
The Linux package attempts to query the underlying system to
check which init system it uses.
This manifests itself as a
WARNING during the
sudo gitlab-ctl reconfigure
Depending on the init system, this
WARNING can be one of:
/sbin/init: unrecognized option '--version'
when the underlying init system is not upstart.
-.mount loaded active mounted /
when the underlying init system IS systemd.
These warnings can be safely ignored. They are not suppressed because this allows everyone to debug possible detection issues faster.