[4.x] Allow a custom static caching url store to be specified

[ryanmitchell]

Static caching stores a cache of mapping of URLs to filenames in the Laravel cache, which is retrieved during invalidation.

However, if you have cleared your Laravel cache (eg artisan cache:clear), this mapping is lost, so no URLs are invalidated.

This PR provides a work around this behaviour by allowing a static_cache cache store to specified, which is then used for storing these urls. This wont be affected by the default cache:clear command, only by php artisan static:clear

Closes #7333

[jasonvarga]

Rather than setting a path and making an explicit FileStore, I think it could be better to let you create a static_cache cache store, and use that if it exists. Like we do for the outpost:

cms/src/Licensing/Outpost.php

Lines 183 to 196 in a0efa08

	private function cache()
	{
	if ($this->store) {
	return $this->store;
	}
	try {
	$store = Cache::store('outpost');
	} catch (InvalidArgumentException $e) {
	$store = Cache::store();
	}
	return $this->store = $store;
	}

[ryanmitchell]

Would that not be the same and remove everything during cache:clear ?

[jasonvarga]

Nope. Only the default store is cleared during cache:clear. You can provide a specific store to the command.

[ryanmitchell]

Ah cool. Didn’t know that. Thanks!

[ryanmitchell]

I've updated that now. Would it make sense for me to PR a change to https://github.com/statamic/statamic/blob/4.x/config/cache.php to include a static_cache store so that the default behaviour is updated?

[jasonvarga]

Would it make sense for me to PR a change to statamic/[email protected]/config/cache.php to include a static_cache store so that the default behaviour is updated

Yes. Make sure that the path is different from the file store - otherwise it will still be affected by cache:clear.