kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/config
History
Vladimir Shushlin c3338c920d Add pages domains acme orders 
Extract acme double to helper

Create ACME challanges for pages domains

* Create order & challange through API
* save them to database
* request challenge validation

We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain

Add controller for processing acme challenges redirected from pages

Don't save acme challenge url - we don't use it

Validate acme challenge attributes

Encrypt private_key in acme orders
2019-06-06 18:55:31 +00:00
..
environments Allow BetterErrors REPL to be enabled 2019-06-05 21:48:44 +10:00
helpers Rename environment variable EE to IS_GITLAB_EE 2019-04-05 12:08:05 +02:00
initializers Merge dev.gitlab.org master into GitLab.com master 2019-06-03 14:56:33 +02:00
locales Add ProjectMetricsDashboardSetting model and table 2019-04-26 17:23:26 +00:00
prometheus Use existing common metrics 2019-04-24 18:23:03 +08:00
routes Abstract auto merge processes 2019-06-03 13:15:29 +07:00
application.rb Upgrade Rails to 5.1.6.1 2019-04-23 08:31:23 +08:00
boot.rb Remove rails 4 support in CI, Gemfiles, bin/ and config/ 2018-12-14 19:36:22 +01:00
database.yml.env
database.yml.example Changes RackAttack logger to use structured logs 2019-05-24 00:45:02 +00:00
database.yml.mysql Set 'staging specific' in database.yml.mysql 2017-10-17 21:12:46 +03:00
database.yml.postgresql Update database.yml.postgresql 2017-10-17 21:15:01 +03:00
dependency_decisions.yml Use GitLab UI area chart 2018-12-07 17:36:17 -05:00
environment.rb Remove rails 4 support in CI, Gemfiles, bin/ and config/ 2018-12-14 19:36:22 +01:00
gitlab.yml.example Add Puma sampler 2019-05-29 12:27:44 +00:00
jsdocs.config.js Generate searchable JSDoc documentation 2019-01-14 21:46:21 +00:00
karma.config.js Merge branch '58869-unified-fe-test-script' into 'master' 2019-05-23 17:32:56 +00:00
license_finder.yml
mail_room.yml
no_todos_messages.yml Improve empty states for TODOs and issues 2017-12-11 12:08:55 +00:00
object_store_settings.rb Make ObjectStoreSettings use more explicit and add specs 2018-07-24 14:44:44 +03:00
puma.example.development.rb Add experimental support for Puma 2018-10-25 17:50:15 +01:00
puma.rb.example Replace Unicorn with web server in the init.d script [ci skip] 2019-05-17 17:00:29 +00:00
README.md
redis.cache.yml.example
redis.queues.yml.example
redis.shared_state.yml.example
resque.yml.example
routes.rb Add pages domains acme orders 2019-06-06 18:55:31 +00:00
secrets.yml.example
settings.rb Ensure that db encryption keys have proper bytesize 2018-11-22 15:35:49 +01:00
sidekiq.yml.example
sidekiq_queues.yml Introduce sidekiq worker for auto merge process 2019-06-04 10:51:32 +07:00
spring.rb [Rails5] Update files by rails app:update 2018-03-22 09:37:57 +11:00
unicorn.rb.example Add experimental support for Puma 2018-10-25 17:50:15 +01:00
unicorn.rb.example.development Remove extra ending line from unicorn example file 2019-05-16 16:24:59 -05:00
webpack.config.js Rename environment variable EE to IS_GITLAB_EE 2019-04-05 12:08:05 +02:00
webpack.config.review_toolbar.js Build visual_review_toolbar with webpack 2019-05-29 20:24:15 +00: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