Fix #1265: Load environment-specific config file

[ma11hew28]

@options[:environment] is a lambda literal.

@options[:environment].call returns the environment string, eg, "development".

[nateberkopec]

👍 Needs a test though.

[nateberkopec]

Ping, happy to merge with a test 👍

[ma11hew28]

I'm sorry. I don't know how to write a test for this, but when I tried it out, it worked for me.

[allaire]

Experiencing this issue as well

[allaire]

I don't understand, going back to puma 3.6.0 fix the environment config not loading bug, but it seems that this version is also using a proc for @options[:environment], which got me thinking it might be something else?

I think #1284 is similar

In my case, on 3.6.0, having exec bundle exec puma -p 5010 in my upstart scripts works and correctly load the right environment file (defined by RACK_ENV).

[nateberkopec]

I think #1340 is a more complete solution.