On Thursday, October 9, 2014 9:04:49 PM UTC-7, binarypaladin wrote:
>
> Awesome. Thanks a bunch.
>
> I'm guessing this has come up before—and it's more of a Rails question 
> than a Sequel question at this point—but is there a good spot in Rails to 
> put the disconnect? I had read in another thread on this board that doing 
> it after the models had loaded made sense, and it does, but do you know of 
> a spot in Rails that executes automatically AFTER eager loading of classes 
> occurs? That seems like the ideal place to do a disconnect.
>

The best place to do it would be in a web server before_fork hook. 
 Unfortunately, unlike unicorn, I don't believe passenger offers such a 
hook.

I think with Rails/Passenger the best place to do it would be at the bottom 
of config/environment.rb or at the bottom of config.ru. 

Thanks,
Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to