Skip to content
New issue

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 environment file is broken since 3.8.0 #1327

Closed
allaire opened this issue Jun 4, 2017 · 3 comments · Fixed by #1340
Closed

Loading environment file is broken since 3.8.0 #1327

allaire opened this issue Jun 4, 2017 · 3 comments · Fixed by #1340
Assignees
Labels

Comments

@allaire
Copy link
Contributor

allaire commented Jun 4, 2017

Loading the right environment file according to the rack environment is broken (https://github.com/puma/puma#configuration-file).

Steps to reproduce

  1. Make sure to create different config/puma/production.rb, config/puma/development.rb file (you can put raise "foo" in the production one)

  2. Run RACK_ENV=production bundle exec puma start

  3. 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

@schneems
Copy link
Contributor

schneems commented Jun 5, 2017

Broken on 3.9 as well?

@allaire
Copy link
Contributor Author

allaire commented Jun 5, 2017

@schneems Yep!

schneems added a commit that referenced this issue Aug 2, 2017
@allaire
Copy link
Contributor Author

allaire commented Aug 3, 2017

@schneems Great catch, thanks for fixing! 🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants