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

Sidekiq assign queue #51

Open
criticerz opened this issue Sep 11, 2015 · 5 comments
Open

Sidekiq assign queue #51

criticerz opened this issue Sep 11, 2015 · 5 comments

Comments

@criticerz
Copy link

I added config.async = :sidekiq to vero.rb, but I'm wondering if I can tell vero which queue to add jobs to?

@criticerz
Copy link
Author

Also, I know you recently merged the pull request for sidekiq integration, but haven't released the gem yet. I had to pull the gem for the git commit. I'm using it in production right now. I'll let you know if I run into any issues with the commit.

@jylamont
Copy link
Contributor

Hey @criticerz, I believe it will use the "default" queue (we don't define sidekiq_options :queue => xxx). Let me know if you hit any snags.

@jylamont
Copy link
Contributor

But we could definitely add the ability define a queue if default is not ideal.

@criticerz
Copy link
Author

Will do. So far it's okay since the jobs are being processed very quickly.
Thanks!

On Fri, Sep 11, 2015 at 2:03 PM, James Lamont notifications@github.com
wrote:

But we could definitely add the ability define a queue if default is not
ideal.


Reply to this email directly or view it on GitHub
#51 (comment).

Alain Fontaine
CTO & Lead Developer at ClutchPrep.com
786-291-1779 | @AlainFV http://www.twitter.com/alainfv | alainfontaine
http://linkedin.com/in/alainfontaine

@shaneog
Copy link
Contributor

shaneog commented Oct 14, 2015

I would love the ability to define the queue. I use a much higher priority for Vero email events than other queues since I am sending transactional emails using Vero.

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

3 participants