Fix sidekiq web UI #2645
Merged
Fix sidekiq web UI #2645
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
Fixes #2638 This PR follows the instructions from the Sidekiq docs: https://github.com/mperham/sidekiq/wiki/Monitoring#rails-api-application-session-configuration It also adds a SECRET_KEY_BASE to the web docker-compose service, which is required now that we switched to RAILS_ENV=production. This value is not used anywhere else, so it seems safe to have here. No .env hijinks needed, I do not think.
ndushay
approved these changes
Apr 2, 2021
jcoyne
approved these changes
Apr 2, 2021
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.
Fixes #2638
Why was this change made?
This PR follows the instructions from the Sidekiq docs: https://github.com/mperham/sidekiq/wiki/Monitoring#rails-api-application-session-configuration
It also adds a SECRET_KEY_BASE to the web docker-compose service, which is required now that we switched to RAILS_ENV=production. This value is not used anywhere else, so it seems safe to have here. No .env hijinks needed, I do not think.
How was this change tested?
CI, locally
Which documentation and/or configurations were updated?
None