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

Update puma.rb generator template to reconcile with Puma documentation #28627

Closed
wants to merge 1 commit into from
Closed

Update puma.rb generator template to reconcile with Puma documentation #28627

wants to merge 1 commit into from

Conversation

zach-taylor
Copy link

Summary

I'm attempting to reconcile some documentation on ActiveRecord connections between Puma's README and the default generated Puma config file in Rails.

What's recommended in the Puma README:

on_worker_boot do
  ActiveSupport.on_load(:active_record) do
    ActiveRecord::Base.establish_connection
  end
end

What's in the default puma.rb:

on_worker_boot do
  ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
end

Other Information

The config was originally added by @schneems here: #23057

Not sure if he had some reasoning behind not using ActiveSupport.on_load (perhaps ActiveRecord will always already be loaded by this point?)

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @pixeltrix (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

@schneems
Copy link
Member

schneems commented Apr 3, 2017

Is there a reason to use "on_load"? What does it buy us?

@zach-taylor
Copy link
Author

zach-taylor commented Apr 4, 2017

@schneems after some additional research, I think the whole point of preloading an application is to load your application once (including ActiveRecord::Base) and use CoW to create the workers. Therefore ActiveRecord::Base should always already be loaded at this point (if you're using ActiveRecord) and this change doesn't make sense.

I think I will open a pull request to Puma instead. Appreciate the time, thanks!

@zach-taylor zach-taylor closed this Apr 4, 2017
@matthewd
Copy link
Member

matthewd commented Apr 4, 2017

Does #28057 render all the current explicit-connection-management advice irrelevant?

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 this pull request may close these issues.

None yet

6 participants