bostonopk.blogg.se

What I really wanted to do is disable the built-in Nginx server and just use my self-managed Apache installation. Later, however, I wanted to setup additional sites on the server using Apache, but now port 80 was already bound to by GitLab’s built-in Nginx web server. Since I had nothing else on the server at that time, everything GitLab setup and configured was sufficient. I installed GitLab CE using the Omnibus package on a new CentOS 6 server. #! The mailbox where incoming mail will end up. #! **With self-hosted email servers, this is usually the user part of the #! **With third party providers, this is usually the full email address.** #! "user" part of the address (before the gitlab_rails = Email account username #! **The placeholder can be omitted but if present, it must appear in the #! to reference the item being replied to. # Configuration Settings for GitLab CE and EE #

#! **The values currently assigned are only examples and ARE NOT the default #! **Configuration settings below are optional.** #! beginning Remove them to enable the setting. #! Configuration settings have a single # followed by a single space at the #! #! More information - Description, Docs, Links, Issues etc. #! differentiate between components of this file and to easily select them using #! The following notations at the beginning of each line may be used to #! redis_sentinel_role redis_master_role redis_slave_role geo_primary_role geo_secondary_role #! The default is to have no roles enabled, which results in GitLab running as an all-in-one instance. #! For more details on configuring external_url see: #! URL on which GitLab will be reachable.

#! settings that can be configured by this file, which may be found at: #! Check out the latest version of this file to know about the different

#! This file is generated during initial installation and **is not** modified