[DOCU-2824] Provide different links for rescue app in on-premise and paas scenarios Created: 05/Sep/23 Updated: 05/Sep/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Alex Mansell |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Documentation page URL: | https://docs.magnolia-cms.com/product-docs/6.2/Modules/List-of-modules/Advanced-cache-modules/Advanced-Cache-Policies-module.html#_changing_default_flush_policy | ||||
| Description |
|
In this section of the cache module docs there's a warn message at the end linking the docs of the rescue app.
There are two different procedures to enable the rescue app, one for paas another for on-premise. The current link refers to the latter. Both links must be provided to avoid confusion in Paas customers in need of this fix. Proposed change: Changes to cache policies and executors are applied immediately. Setting incorrect values can render the Magnolia instance inaccessible. If this happens, try the Groovy Rescue app (Instructions for on-premise installations / Instructions for Paas customers) . |