Ability to set a custom prefix for the redis keys. #459
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.
It's possible that multiple applications will want to use the same Redis instance as their queue storage. Right now all queues and jobs are layered on top of each other. This allows adding a custom prefix to the beginning of all Redis keys used in a particular application.
Also, it looks like my clean-up scripts changed all the
assertEquals
toassertEqual
per deprecation of the alias.