README.md in tomo-plugin-sidekiq-1.1.3 vs README.md in tomo-plugin-sidekiq-1.2.0
- old
+ new
@@ -4,10 +4,12 @@
[](https://app.circleci.com/pipelines/github/mattbrictson/tomo-plugin-sidekiq?branch=main)
[](https://codeclimate.com/github/mattbrictson/tomo-plugin-sidekiq)
This is a [tomo](https://github.com/mattbrictson/tomo) plugin that provides tasks for managing [sidekiq](https://github.com/mperham/sidekiq) via [systemd](https://en.wikipedia.org/wiki/Systemd), based on the recommendations in the sidekiq documentation. This plugin assumes that you are also using the tomo `rbenv` and `env` plugins, and that you are using a systemd-based Linux distribution like Ubuntu 18 LTS.
+**This plugin requires Sidekiq 6.0.6 or newer.**
+
---
- [Installation](#installation)
- [Settings](#settings)
- [Tasks](#tasks)
@@ -48,11 +50,11 @@
end
```
### enable-linger
-This plugin installs sidekiq as a user-level service using systemctl --user. This allows sidekiq to be installed, started, stopped, and restarted without a root user or sudo. However, when provisioning the host you must make sure to run the following command as root to allow the sidekiq process to continue running even after the tomo deploy user disconnects:
+This plugin installs sidekiq as a user-level service using `systemctl --user`. This allows sidekiq to be installed, started, stopped, and restarted without a root user or sudo. However, when provisioning the host you must make sure to run the following command as root to allow the sidekiq process to continue running even after the tomo deploy user disconnects:
```
# run as root
$ loginctl enable-linger <DEPLOY_USER>
```
@@ -132,12 +134,9 @@
```yaml
---
:queues:
- default
- - mailers
- - active_storage_analysis
- - active_storage_purge
:concurrency: <%= ENV.fetch("SIDEKIQ_CONCURRENCY", "1") %>
```
Now you can tune sidekiq for each environment by simply setting environment variables (e.g. using `tomo run env:set`), without hard-coding configuration in git or within systemd files.