- 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 Omnibus GitLab 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 Omnibus GitLab release. Usually, this is 0. This is incremented if we need to build a new package without changing the GitLab version.|
The Omnibus GitLab 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 Omnibus GitLab 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
Configuration file in
/etc/gitlab/gitlab.rb is created on initial installation
of the Omnibus GitLab package. On subsequent package upgrades, the configuration
file is not updated with new configuration. This is done to avoid
accidental overwrite of user configuration provided in
New configuration options are noted in the
The Omnibus GitLab package also provides 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.
Omnibus GitLab 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.