Wrong command in docs to start Gitlab Rails console
Problem to solve
The docs for the rails console have a incorrect command to start the rails console for source installs.
Further details
I tried to make a MR but gitlab after 10 minutes forking made me and empty fork and whenever I click edit now on the md document, I can make edits but when I try to commit, it throws an error 500.
Proposal
The command to start the rails console is
sudo -u git -H bundle exec rails console RAILS_ENV=production
it should be changed to:
sudo -u git -H bundle exec rails console -e production
Who can address the issue
Anyone, I guess... Would've done myself if gitlab.com would actually fork properly and not constantly error.