kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/config
History
Filipa Lacerda 485cb91c2f Merge branch 'master' into 31050-registry-image-lists 
* master: (62 commits)
  Fix a dash being rendered in the note's access role
  Remove dead `Gitlab::Markdown::Pipeline` class
  Add CHANGELOG entry
  Fix locked shared runners problem
  Document manual cleanup after background migration stealing
  Removes cycle analytics service and store from global namespace
  Fix PG::UniqueViolation external_email migration
  Migrate Gitlab::Git::Repository#log to Gitaly
  Check for exec permissions also in app/
  Add check for exec permissions and refactor lint doc script
  Update tests to reflect `user_avatar_without_link` helper changes
  Change mode to 644 for all md and png files
  Add instructions for upgrading from CE to EE using GitLab Omnibus chart - docs
  Add `data-src` when image is to be lazy loaded, use `tag` helper instead of `image_tag` helper
  Remove unnecessary use of `gsub`
  Fixed few gitlab:check tasks that were failing with exception
  Update CHANGELOG.md for 10.0.1
  Remove Grit settings from default settings
  Fix duplicate key errors in PostDeployMigrateUserExternalMailData migration
  Improve list of sorting options
  ...
2017-09-26 10:39:36 +01:00
..
environments Fix logger disabling on the CI: instantiate an ActiveSupport::TaggedLogging 2017-07-20 11:16:12 +02:00
initializers Remove Grit settings from default settings 2017-09-23 20:37:26 -04:00
locales
prometheus Fix ingress query 2017-09-09 00:50:02 -04:00
routes Add ContainerTag and ContainerRepository frontend API 2017-09-21 12:21:50 +02:00
application.rb Expand filtered parameters to include token 2017-09-10 07:05:55 -07:00
aws.yml.example
boot.rb Update Prometheus gem to version that explicitly calls munmap 2017-07-19 08:54:39 +00:00
database.yml.env
database.yml.mysql Disabled prepared statements in test 2017-07-10 20:38:26 -07:00
database.yml.postgresql Disabled prepared statements in test 2017-07-10 20:38:26 -07:00
dependency_decisions.yml Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00:00
environment.rb
gitlab.yml.example Removed two legacy config options 2017-09-21 22:04:49 -04:00
karma.config.js disable webpack.optimize.ModuleConcatenationPlugin during karma tests 2017-08-21 13:43:12 -05:00
license_finder.yml
mail_room.yml Support multiple Redis instances based on queue type 2017-07-11 03:35:47 +00:00
no_todos_messages.yml
README.md Support multiple Redis instances based on queue type 2017-07-11 03:35:47 +00:00
redis.cache.yml.example Support multiple Redis instances based on queue type 2017-07-11 03:35:47 +00:00
redis.queues.yml.example Support multiple Redis instances based on queue type 2017-07-11 03:35:47 +00:00
redis.shared_state.yml.example Support multiple Redis instances based on queue type 2017-07-11 03:35:47 +00:00
resque.yml.example
routes.rb Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into ee_issue_928_backport 2017-09-06 14:35:58 +10:00
secrets.yml.example
sidekiq.yml.example
sidekiq_queues.yml Stop using Sidekiq for updating Key#last_used_at 2017-09-20 14:24:14 +02:00
svg.config.js Resolve "Better SVG Usage in the Frontend" 2017-09-22 08:39:47 +00:00
unicorn.rb.example Update prometheus client gem to fix problems with PID handling following 2017-07-27 14:40:36 +02:00
unicorn.rb.example.development
webpack.config.js Merge branch 'master' into 31050-registry-image-lists 2017-09-26 10:39:36 +01:00

README.md

Configuration files Documentation

Note that most configuration files (config/*.*) committed into gitlab-ce will not be used for omnibus-gitlab. Configuration files committed into gitlab-ce are only used for development.

gitlab.yml

You can find most of GitLab configuration settings here.

mail_room.yml

This file is actually an YML wrapped inside an ERB file to enable templated values to be specified from gitlab.yml. mail_room loads this file first as an ERB file and then loads the resulting YML as its configuration.

resque.yml

This file is called resque.yml for historical reasons. We are NOT using Resque at the moment. It is used to specify Redis configuration values when a single database instance of Redis is desired.

Advanced Redis configuration files

In more advanced configurations of Redis key-value storage, it is desirable to separate the keys by lifecycle and intended use to ease provisioning and management of scalable Redis clusters.

These settings provide routing and other configuration data (such as sentinel, persistence policies, and other Redis customization) for connections to Redis single instances, Redis sentinel, and Redis clusters.

If desired, the routing URL provided by these settings can be used with:

  1. Unix Socket
    1. named socket for each Redis instance desired.
    2. database number for each Redis instance desired.
  2. TCP Socket
    1. host name or IP for each Redis instance desired
    2. TCP port number for each Redis instance desired
    3. database number for each Redis instance desired

Example URL attribute formats for GitLab Redis .yml configuration files

  • Unix Socket, default Redis database (0)
    • url: unix:/path/to/redis.sock
    • url: unix:/path/to/redis.sock?db=
  • Unix Socket, Redis database 44
    • url: unix:/path/to/redis.sock?db=44
    • url: unix:/path/to/redis.sock?extra=foo&db=44
  • TCP Socket for Redis on localhost, port 6379, database 33
    • url: redis://:mynewpassword@localhost:6379/33
  • TCP Socket for Redis on remote host myserver, port 6379, database 33
    • url: redis://:mynewpassword@myserver:6379/33

redis.cache.yml

If configured, redis.cache.yml overrides the resque.yml settings to configure the Redis database instance used for Rails.cache and other volatile non-persistent data which enhances the performance of GitLab. Settings here can be overridden by the environment variable GITLAB_REDIS_CACHE_CONFIG_FILE which provides an alternate location for configuration settings.

The order of precedence for the URL used to connect to the Redis instance used for cache is:

  1. URL from a configuration file pointed to by the GITLAB_REDIS_CACHE_CONFIG_FILE environment variable
  2. URL from redis.cache.yml
  3. URL from a configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. URL from resque.yml
  5. redis://localhost:6380

The order of precedence for all other configuration settings for cache are selected from only the first of the following files found (if a setting is not provided in an earlier file, the remainder of the files are not searched):

  1. the configuration file pointed to by the GITLAB_REDIS_CACHE_CONFIG_FILE environment variable
  2. the configuration file redis.cache.yml
  3. the configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. the configuration file resque.yml

redis.queues.yml

If configured, redis.queues.yml overrides the resque.yml settings to configure the Redis database instance used for clients of ::Gitlab::Redis::Queues. These queues are intended to be the foundation of reliable inter-process communication between modules, whether on the same host node, or within a cluster. The primary clients of the queues are SideKiq, Mailroom, CI Runner, Workhorse, and push services. Settings here can be overridden by the environment variable GITLAB_REDIS_QUEUES_CONFIG_FILE which provides an alternate location for configuration settings.

The order of precedence for the URL used to connect to the Redis instance used for queues is:

  1. URL from a configuration file pointed to by the GITLAB_REDIS_QUEUES_CONFIG_FILE environment variable
  2. URL from redis.queues.yml
  3. URL from a configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. URL from resque.yml
  5. redis://localhost:6381

The order of precedence for all other configuration settings for queues are selected from only the first of the following files found (if a setting is not provided in an earlier file, the remainder of the files are not searched):

  1. the configuration file pointed to by the GITLAB_REDIS_QUEUES_CONFIG_FILE environment variable
  2. the configuration file redis.queues.yml
  3. the configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. the configuration file resque.yml

redis.shared_state.yml

If configured, redis.shared_state.yml overrides the resque.yml settings to configure the Redis database instance used for clients of ::Gitlab::Redis::SharedState such as session state, and rate limiting. Settings here can be overridden by the environment variable GITLAB_REDIS_SHARED_STATE_CONFIG_FILE which provides an alternate location for configuration settings.

The order of precedence for the URL used to connect to the Redis instance used for shared_state is:

  1. URL from a configuration file pointed to by the GITLAB_REDIS_SHARED_STATE_CONFIG_FILE environment variable
  2. URL from redis.shared_state.yml
  3. URL from a configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. URL from resque.yml
  5. redis://localhost:6382

The order of precedence for all other configuration settings for shared_state are selected from only the first of the following files found (if a setting is not provided in an earlier file, the remainder of the files are not searched):

  1. the configuration file pointed to by the GITLAB_REDIS_SHARED_STATE_CONFIG_FILE environment variable
  2. the configuration file redis.shared_state.yml
  3. the configuration file pointed to by the GITLAB_REDIS_CONFIG_FILE environment variable
  4. the configuration file resque.yml