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

Rails 5.0 incompatibilities #12

Open
mensfeld opened this issue Feb 19, 2016 · 6 comments
Open

Rails 5.0 incompatibilities #12

mensfeld opened this issue Feb 19, 2016 · 6 comments

Comments

@mensfeld
Copy link

Apartment sidekiq is no longer working out of the box with the new Rails.

In order to make it work I had to manually invoke:

require 'apartment/sidekiq/railtie'
Apartment::Sidekiq::Middleware.run
@arwaahmed
Copy link

@mensfeld Facing the same issue here, i placed your snippet in an initalizer and it is still not working. Any hints?

@mensfeld
Copy link
Author

@arwaahmed unfortunately I decided not to go with Apartment as in the end I had to start doing multiple hacks to make it work. Until it is supported I would not recommend using Apartment with Rails5.

@jhubert
Copy link

jhubert commented Aug 28, 2017

@mensfeld What did you use instead?

@jhubert
Copy link

jhubert commented Aug 28, 2017

@bradrobertson Are you aware of this? Anything we can do to help?

@mensfeld
Copy link
Author

@jhubert I decided to go a different road ;)

@hcurotta
Copy link

Hi there. Are we likely to see Rails 5 supported?

I've taken the approach linked in one of the other threads, passing the tenant to the jobs explicitly, but gems like SearchKick queue up jobs automatically and I can't cleanly wedge the tenant name into the callback.

Would be great to know if there are any other recommended approaches. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants