Commit graph

9 commits

Author SHA1 Message Date
GitLab Bot
d081e00aa7 Add latest changes from gitlab-org/gitlab@master 2020-06-24 12:09:24 +00:00
GitLab Bot
4f5c8572e9 Add latest changes from gitlab-org/gitlab@master 2020-06-16 18:09:01 +00:00
GitLab Bot
6744162376 Add latest changes from gitlab-org/gitlab@master 2020-06-15 12:08:44 +00:00
GitLab Bot
810bd2a662 Add latest changes from gitlab-org/gitlab@master 2020-06-02 12:08:33 +00:00
GitLab Bot
80f61b4035 Add latest changes from gitlab-org/gitlab@master 2019-09-18 14:02:45 +00:00
Vladimir Shushlin
4687ff7c9b Store Let's Encrypt private key in settings
Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package

* Revert "Generate Let's Encrypt private key"
  This reverts commit 444959bfa0.

* Add Let's Encrypt private key to settings
  as encrypted attribute

* Generate Let's Encrypt private key
  in database migration
2019-05-28 04:47:34 +00:00
Stan Hu
33aa185d83 Add warning about updating Omnibus is secrets are updated
[ci skip]
2019-05-10 13:41:32 -05:00
Vladimir Shushlin
444959bfa0 Generate Let's Encrypt private key 2019-05-09 13:45:25 +00:00
Stan Hu
b5c706326a Upgrade to Ruby 2.4.4
Fixes that make this work:

* A change in Ruby (ce635262f5)
requires passing in the exact required length for OpenSSL keys and IVs.

* Ensure the secrets.yml is generated before any prepended modules are
loaded. This is done by renaming the `secret_token.rb` initializer to
`01_secret_token.rb`, which is a bit ugly but involves the least impact on
other files.
2018-05-29 15:19:33 -07:00
Renamed from config/initializers/secret_token.rb (Browse further)