sameersbn / sameersbn/docker-gitlab
invalid DB_PASS in database_configuration
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi folks,
I got the following error log in /home/git/gitlab/log/unicorn.stderr.log when starting gitlab container where DB_PASS="<%password%>".
(erb):13:in <main>': Cannot load Rails.application.database_configuration: (NameError)
uninitialized constant password
from /usr/lib/ruby/2.3.0/erb.rb:864:in eval'
from /usr/lib/ruby/2.3.0/erb.rb:864:in result'
from /home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application/configuration.rb:104:in database_configuration'
Maybe there are some characters need to be escaped.
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 by reproducing the GitLab container startup with the reported DB_PASS value and inspect /home/git/gitlab/log/unicorn.stderr.log. Trace how Rails loads database_configuration and determine what “done” means for passwords containing these characters: startup should load the configuration without the reported NameError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ruby
- Domain
- database, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100