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.

Sign up for GitHub

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

Jump to bottom

Section about ActiveJob and job processors like Sidekiq or Resque #9

Closed
skryking opened this issue Jul 22, 2016 · 1 comment
Closed

Section about ActiveJob and job processors like Sidekiq or Resque #9

skryking opened this issue Jul 22, 2016 · 1 comment

Comments

@skryking
Copy link

I noticed no mention of background job processors like sidekiq or resque was this on purpose?
@iJackUA
Copy link
Owner

iJackUA commented Jul 22, 2016

It is because I do not know any big issue with this to write a caution for.
This is not just another "awesome-ruby" where I list all known gems for any case, but only when I know where to propose less magic solution :)

I could make a section about "ActiveJob" caution and mention job runners there.
If you have any ideas what to cover - suggest please.

@iJackUA iJackUA changed the title I noticed no mention of background job processors like sidekiq or resque was this on purpose? Section about ActiveJob and job processors like Sidekiq or Resque Jul 22, 2016
iJackUA added a commit that referenced this issue Jul 27, 2016
@iJackUA
#9, Sync Wed Jul 27 10:21:44 UTC 2016
4b16fa8
@iJackUA iJackUA closed this as completed in fe2d148 Aug 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iJackUA @skryking