-
Notifications
You must be signed in to change notification settings - Fork 307
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
implemented ability to split sidekiq_roles by count of sidekiq-processes #45
Conversation
Nice! Can you update the Readme with an example ? |
Yes, sure! I did it. |
I just noticed that only for capistrano2. We need to support cap 3 |
Ok. I'll implement same logic for capistrano 3. |
+1 |
any update on this PR? |
Hey, guys. I've implemented support of cap3. |
Great job. Could you add an entry to the changelog ? |
+1 fot this PR |
Hey, guys. Do you have any update about my PR? |
implemented ability to split sidekiq_roles by count of sidekiq-processes
+1 for
Currently my assumption is if I have
then the |
Now we can customize how many processes capistrano has to run on each server.
set :sidekiq_role, [:sidekiq, :sidekiq_small, :sidekiq_big]
set :sidekiq_small_processes, 2
set :sidekiq_big_processes, 4
role :sidekiq, 'sidekiq.example.com'
role :sidekiq_small, 'sidekiq_small.example.com'
role :sidekiq_big, 'sidekiq_big.example.com'
It was very helpfull for me because we use different AWS-S3 instancess for sidekiq. I hope it will be helpfull for other developers.