[5.x] Allow custom nocache db connection #11716
Merged
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.
The Problem
Users cannot specify a separate database connection for the nocache_regions table without modifying Statamic core code. Sometimes, this table can get really big and you may not want to include it on frequent backups. You may also want to move this table specifically closer to the Statamic install to reduce latency.
The Solution
This PR adds a configuration option to allow specifying a different database connection for the
nocache_regions
table.Backward Compatibility
This change is fully backward compatible as it defaults to the current behavior (using the default database connection) when no configuration is provided.
Usage Example