This project creates full-stack platform-specific downloadable packages for GitLab. For other installation options please see the GitLab installation page.
The source of omnibus-gitlab is hosted on GitLab.com and there are mirrors to make contributing as easy as possible.
The documentation can be found in the doc directory.
Omnibus GitLab is using a fork of omnibus project. For additional information see the comments in the Gemfile.
We left the links below in the readme to preserve old links, but please use the doc directory to browse the complete documentation.
Please see the contribution guidelines
Please follow the steps on the downloads page.
Your GitLab instance should be reachable over HTTP at the IP or hostname of your server. You can login as an admin user with username root and password 5iveL!fe.
See doc/maintenance/index.md for useful commands to control/debug your GitLab instance.
See doc/settings/configuration.md.
Configuring the external URL for GitLabSee doc/settings/configuration.md.
Storing Git data in an alternative directorySee doc/settings/configuration.md.
Changing the name of the Git user / groupSee doc/settings/configuration.md.
See doc/settings/ldap.md.
RedirectHTTP requests to HTTPS
Change the default port and the ssl certificate locations
Use non-packaged web-server
For using an existing Nginx, Passenger, or Apache webserver see doc/settings/nginx.md.
Using a non-packaged PostgreSQL database management serverTo connect to an external PostgreSQL DBMS see doc/settings/database.md
Using a non-packaged Redis instance Adding ENV Vars to the Gitlab Runtime EnvironmentSee doc/settings/environment-variables.md.
Changing gitlab.yml settingsSee doc/settings/gitlab.yml.md.
Specify numeric user and group identifiersSee doc/settings/configuration.md.
Sending application email via SMTPSee doc/settings/smtp.md.
Omniauth (Google, Twitter, GitHub login)Omniauth configuration is documented in docs.gitlab.com.
Adjusting Unicorn settings Setting the NGINX listen address or addresses Inserting custom NGINX settings into the GitLab server block Inserting custom settings into the NGINX config Only start omnibus-gitlab services after a given filesystem is mountedSee doc/settings/configuration.md.
Instructions for updating your Omnibus installation and upgrading from a manual installation are in the update directory.
Uninstalling Omnibus GitLabSee doc/installation/_index.md.
Common installation problemsThis section has been moved to the separate document doc/troubleshooting.md.
Section below remains for historical reasons(mainly to not break existing links). Each section contains the link to the new location.
Apt error 'The requested URL returned error: 403' GitLab is unreachable in my browser Emails are not being delivered TCP ports for GitLab services are already taken Git SSH access stops working on SELinux-enabled systems Postgres error 'FATAL: could not create shared memory segment: Cannot allocate memory' Reconfigure complains about the GLIBC version Reconfigure fails to create the git user Failed to modify kernel parameters with sysctl I am unable to install omnibus-gitlab without root access gitlab-rake assets:precompile fails with 'Permission denied' 'Short read or OOM loading DB' error Backup and restore omnibus-gitlab configuration Creating an application backup Restoring an application backup Backup and restore using non-packaged databaseIf you are using non-packaged database see documentation on using non-packaged database.
Upload backups to remote (cloud) storageFor details check backup documentation.
See doc/maintenance/_index.md.
Omnibus-gitlab uses four different directories.
/opt/gitlab holds application code for GitLab and its dependencies./var/opt/gitlab holds application data and configuration files that gitlab-ctl reconfigure writes to./etc/gitlab holds configuration files for omnibus-gitlab. These are the only files that you should ever have to edit manually./var/log/gitlab contains all log data generated by components of omnibus-gitlab.Although omnibus-gitlab runs on systems that have SELinux enabled, it does not use SELinux confinement features:
The correct operation of Git access via SSH depends on the labeling of /var/opt/gitlab/.ssh. If needed you can restore this labeling by running sudo gitlab-ctl reconfigure.
Depending on your platform, gitlab-ctl reconfigure will install SELinux modules required to make GitLab work. These modules are listed in files/gitlab-selinux/README.md.
NSA, if you're reading this, we'd really appreciate it if you could contribute back a SELinux profile for omnibus-gitlab :) Of course, if anyone else is reading this, you're welcome to contribute the SELinux profile too.
This section has been moved to separate document doc/settings/logs.md.
Tail logs in a console on the serverSee doc/settings/logs.md.
See doc/settings/logs.md.
See doc/settings/logs.md.
UDP log shipping (GitLab Enterprise Edition only) Create a user and database for GitLab Configure omnibus-gitlab to connect to it Seed the database (fresh installs only) Building your own packageSee the separate build documentation.
Running a custom GitLab versionIt is not recommended to make changes to any of the files in /opt/gitlab after installing omnibus-gitlab: they will either conflict with or be overwritten by future updates. If you want to run a custom version of GitLab you can build your own package or use another installation method.
This omnibus installer project is based on the awesome work done by Chef in omnibus-chef-server.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4