sameersbn / sameersbn/docker-gitlab
Missing Rails.application.secrets.otp_key_base for production environment
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
This has actually been happening for a few releases now. When I start gitlab, after Migrating database... I get a entry of:
Missing Rails.application.secrets.jws_private_key for production environment. The secret will be generated and stored in config/secrets.yml.
is there something I need to do for a persistent secret?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with config/secrets.yml and the production startup output around database migration. Trace how otp_key_base and jws_private_key are handled for the production environment, then verify the behavior across a restart. Done means the persistent-secret requirement and expected configuration are clear and the warning is resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rails, ruby
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100