Support OpenSRF+Redis for Evergreen 3.12
Bug #2041431 reported by
Bill Erickson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Spawned from bug #2017941
Bug for tracking Evergreen 3.12 patches to better support installing Evergreen 3.12 atop OpenSRF+Redis for new installations.
Changed in evergreen: | |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbergja) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp2041431- opensrf- on-redis- v3-eg3. 12
* Adds commented-out Redis config options to opensrf_ core.xml. example
* Docs for switching EG configs to Redis
Note these changes are only needed for EG 3.12 where it's assumed that Ejabberd is the default, but Redis is supported. Post-3.12, where Redis is the default OpenSRF variant for new installations, the configs in bug #2017941 will just work. In theory, we don't need multi-flavor instructions (Redis vs. Ejabberd) for new EG installs post EG 3.12, but they can be added if needed.