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
Breaking change to Rack::Timeout causes Heroku deployment failure #918
Comments
Based on the README it seems like the recommended way to modify the timeout is now through environment variables. Two questions:
|
Hey Oren, nice to see you again (we met at the last RailsConf). I would be happy to help you get this through. Are you ready to make a PR, or would you like any help? |
I would suggest just using the new defaults for Rack::Timeout, as the new config would require all 4 variables to be set to https://github.com/heroku/rack-timeout/blob/master/README.md#configuring Rack::Timeout takes the following settings, shown here with their default values and associated environment variables.
These settings can be overriden during middleware initialization or environment variables RACK_TIMEOUT_* mentioned above. Middleware parameters take precedence:
|
@composerinteralia great to hear from you and congrats on the new gig 😄! I'm happy to open a PR - I just wanted to make sure my approach above made sense. To @toobulkeh's point, it looks like the old I'll throw a PR up and we can move this discussion there. Thanks! |
Resolves thoughtbot#918 Rack::Timeout v0.5.0 removed legacy setter methods used for configuration (zombocom/rack-timeout#125) such that the configuration added by Suspenders causes a NoMethodError when initializing Rails in the production environment (e.g. during Heroku deployment). This PR switches to using environment variable-based configuration of Rack::Timeout, matching the recommendations in the README.
Resolves #918 Rack::Timeout v0.5.0 removed legacy setter methods used for configuration (zombocom/rack-timeout#125) such that the configuration added by Suspenders causes a NoMethodError when initializing Rails in the production environment (e.g. during Heroku deployment). This PR switches to using environment variable-based configuration of Rack::Timeout, matching the recommendations in the README.
See here for more info. It looks like we can just update this file - I can try to open up a PR later tonight. Thanks!
The text was updated successfully, but these errors were encountered: