[5.x] Allow addons cache path to be set by an environment variable #11365
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.
When deploying on Vercel I'm running into an issue with the addon cache not being writeable as its hard coded to boostrap/cache/addons.php
Laravel allow environment variables to be set to override their cache paths - see examples at:
https://github.com/laravel/framework/blob/2e5054a19ba55b335bf8df43a8ae7e032244f671/src/Illuminate/Foundation/Application.php#L1256-L1269
This PR adds support for a
STATAMIC_ADDONS_CACHE
environment variable to set the path to this cache, in the same way Laravel allows, for exampleSTATAMIC_ADDONS_CACHE="/tmp/addons.php"
. This will allow deploying on Vercel to work again.Ideally we'd use their normalizeCachePath() function but it's not public.