We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading the right environment file according to the rack environment is broken (https://github.com/puma/puma#configuration-file).
Make sure to create different config/puma/production.rb, config/puma/development.rb file (you can put raise "foo" in the production one)
config/puma/production.rb
config/puma/development.rb
raise "foo"
Run RACK_ENV=production bundle exec puma start
RACK_ENV=production bundle exec puma start
Puma loads development configuration (or at least doesn't load the RACK_ENV's configuration file)
Puma should load the right environment file according to the RACK_ENV variable.
Puma isn't loading the environment file, even if it shows the right env in the start message. I think it's related to @schneems 's refactor here #1234
It works correctly on puma 3.7.x.
It works correctly when we manually specify the configuration file using -C switch.
-C
Ruby version: 2.2.2 Rails version: 4 & 5
The text was updated successfully, but these errors were encountered:
Broken on 3.9 as well?
Sorry, something went wrong.
@schneems Yep!
0584a33
Merge pull request #1383 from puma/schneems/fix-double-binds
d31d68a
[close #1327] Fix double port bind in Rails
@schneems Great catch, thanks for fixing! 🍻
schneems
Successfully merging a pull request may close this issue.
Loading the right environment file according to the rack environment is broken (https://github.com/puma/puma#configuration-file).
Steps to reproduce
Make sure to create different
config/puma/production.rb
,config/puma/development.rb
file (you can putraise "foo"
in the production one)Run
RACK_ENV=production bundle exec puma start
Puma loads development configuration (or at least doesn't load the RACK_ENV's configuration file)
Expected behavior
Puma should load the right environment file according to the RACK_ENV variable.
Actual behavior
Puma isn't loading the environment file, even if it shows the right env in the start message. I think it's related to @schneems 's refactor here #1234
It works correctly on puma 3.7.x.
It works correctly when we manually specify the configuration file using
-C
switch.System configuration
Ruby version: 2.2.2
Rails version: 4 & 5
The text was updated successfully, but these errors were encountered: