lets_encrypt_private_key may not be initialized on clean install
@vshushlin From https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28353, I just thought of this: Since lets_encrypt_private_key
is now generated in the migration, a new install may not get this value since the schema will be initialized with db/schema.rb
.
I think we either want to:
- Bring back the old on-the-fly generation of
lets_encrypt_private_key
- Initialize
lets_encrypt_private_key
with the other secrets at init time
We probably want to check Gitlab::Database.read_only?
.
Edited by Vladimir Shushlin