[orangelight] Add sidekiq #5712
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Max Kadel <[email protected]>
- This reduces duplication of running roles when running the playbook, and fixes a bug with the deploy_user role when we run the sidekiq role on a subset of boxes Co-authored-by: Jane Sandberg <[email protected]>
kayiwa
reviewed
Jan 9, 2025
| @@ -22,6 +22,7 @@ | |||
| run_once: true | |||
| tags: update_keys | |||
kayiwa
approved these changes
Jan 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connected to pulibrary/orangelight#4609
This adds the sidekiq role to the orangelight playbook. A few things to note:
ruby_stasks would run twice: first for the sidekiq boxes, then again for non-sidekiq boxes. Now that they are in the playbook, placed before thesidekiqrole,ruby_s(and other tasks likebind9) only run once.sidekiq_worker_namedoes not contain the name of the application, as it does for bibdata. This is so we can simply runsystemctl restart sidekiq, rather than having to figure out the application-specific sidekiq name.