* Prevent AR middleware and reloader clash
The ActiveRecord middleware releases any current ActiveRecord
connections before the reloader has a chance to clear their query
caches.
We can just remove this middleware because the reloader takes care of
clearing active connections, too.
* Make sure folks haven't added the middleware manually
* Fix the conditional
* Mention that the reloader also clears connections
* Move it all back into a single method
* Typos
* Pull all rails setup into railtie
* Set the middleware even earlier
Also clarify exactly when these hooks are run.
* Only check ActiveRecord reloader/middleware sanity at boot
Checking if the constant is define and including the extensions directly
in the base class will for the class to be loaded. This may cause these
components to be loaded before the time and be missconfigured if the
sidekiq railtie is loaded before the components railtie.
It is unlikely to happen but is better be safe.
Replaced with `__send__` from std lib
* `send` can now be overridden to be more semantically meaningful
* `message.send(user_id)` as opposed to `message.send_message(user_id)`
* `__send__` makes it clear that the reflective version is intended
Workers are the user's classes, the threads are now called processors. Add secret sauce to make Rails config much easier. Use a railtie to auto-add app/workers to the autoload path.