Feature #33589
closed
How to install and configure Sidekiq as queuing backend
0%
Description
I've created the following Wiki page with instruction about how to install and configure Sidekiq:
Please let me know what do you think and where we should link the page.
Updated by pasquale [:dedalus] almost 5 years ago
Hi Marius, I read the wiki and it is really well documented. Thanks!
Updated by Bernhard Rohloff almost 5 years ago
Very cool! Thank you for sharing this. I'll can't wait to give it a try. :-)
Updated by Mischa The Evil almost 5 years ago
I think this is a good howto for setting up these components. I suggest to categorize and link it as such.
Maybe beyond the intended scope of this issue, but I think we also need some short mentions under RedmineInstall#Optional-components and RedmineInstall#Optional-dependencies, and a short description under RedmineInstall#Configuration with a link to a separate wiki page which should contain a (more) generic, more detailed description of (the handling of) background jobs in Redmine specific (e.g. what is handled by background jobs [also thinking about proposed #31076 here]) and Rails in general (how does Redmine relate to Rails in this area [via ActiveMailer, ActiveJob, Queues/QueueAdapters, 3rd-party queuing backends]). This should not be tied specifically to persistent, 3rd-party queuing backends, also the default in-process queuing implementation needs some coverage (see e.g. #31939, #31957).
Additionally, some info for plugin developers would be nice too.
Updated by
Updated by David Doležal over 4 years ago
Is it possible to solve it under Windows-server? My configuration of Redmine:
Environment:
Redmine version 4.1.1.stable
Ruby version 2.6.6-p146 (2020-03-31) [x64-mingw32]
Rails version 5.2.4.2
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp
Updated by David Doležal over 4 years ago
David Doležal wrote:
Is it possible to solve it under Windows-server? My configuration of Redmine:
Environment:
Redmine version 4.1.1.stable
Ruby version 2.6.6-p146 (2020-03-31) [x64-mingw32]
Rails version 5.2.4.2
Environment production
Database adapter Mysql2
Mailer queue ActiveJob::QueueAdapters::AsyncAdapter
Mailer delivery smtp
My problem was diffrent. It was in connector on SMTP server, where was set low limit emails per minute from IP address. So simple! It works with Async and SuckerPunch. So I think it will work with Sidekiq too.
Updated by Marius BĂLTEANU over 1 year ago
- Status changed from New to Closed
- Target version deleted (
Candidate for next major release) - Resolution set to Fixed
Mischa The Evil wrote in #note-4:
I think this is a good howto for setting up these components. I suggest to categorize and link it as such.
Maybe beyond the intended scope of this issue, but I think we also need some short mentions under RedmineInstall#Optional-components and RedmineInstall#Optional-dependencies, and a short description under RedmineInstall#Configuration with a link to a separate wiki page which should contain a (more) generic, more detailed description of (the handling of) background jobs in Redmine specific (e.g. what is handled by background jobs [also thinking about proposed #31076 here]) and Rails in general (how does Redmine relate to Rails in this area [via ActiveMailer, ActiveJob, Queues/QueueAdapters, 3rd-party queuing backends]). This should not be tied specifically to persistent, 3rd-party queuing backends, also the default in-process queuing implementation needs some coverage (see e.g. #31939, #31957).
Additionally, some info for plugin developers would be nice too.
For now I made only the short mentions and I've linked the page to RedmineInstall. For the rest of the requirements, we should open a new issue.
Updated by Renaud GOSSE 8 months ago
Hello
Thank you for your tutorial, it was not working on my side, the mails were not sent:
I ran into this issue #69656 and this solved the problem, now the command to run sidekiq is :
bundle exec sidekiq -q default -q mailers
Also I used Valkey instead of Redis and it worked directly without configuration
Cheers !