Andreas Reinhold / reiniandClaude Opus 4.8
1ebd51248e
Bump laravel/framework to ^13.0 and laravel/tinker to ^3.0 per the 12.x to 13.0 upgrade guide. php ^8.5 already satisfied the new minimum. Transitively picks up Fortify 1.37.3, Octane 2.18.0, Livewire 4.3.3, Mary 2.9.7 and Pest 4.7.5, all of which already declare ^13.0 support. Add 'serializable_classes' => false to config/cache.php. When the key is absent it defaults to null, which leaves unserialize() unrestricted; false blocks object deserialization so a leaked APP_KEY cannot be used to drive a gadget chain through the cache. Safe here as no app code uses the cache. Audited every breaking change in the guide against the codebase with no hits: VerifyCsrfToken/ValidateCsrfToken (now PreventRequestForgery), JobAttempted->exceptionOccurred, QueueBusy->$connection, pagination::default, Js::from and array_first/array_last. config/cache.php and config/database.php already used the new hyphenated prefixes, so cache keys and session cookies are unchanged and nothing invalidates on deploy. Verified: 123 tests pass (306 assertions), migrations apply cleanly, and /up, /login and the Livewire asset all serve 200 over HTTP. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
131 lines
4.1 KiB
PHP
131 lines
4.1 KiB
PHP
<?php
|
|
|
|
use Illuminate\Support\Str;
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Cache Store
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This option controls the default cache store that will be used by the
|
|
| framework. This connection is utilized if another isn't explicitly
|
|
| specified when running a cache operation inside the application.
|
|
|
|
|
*/
|
|
|
|
'default' => env('CACHE_STORE', 'database'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Cache Stores
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you may define all of the cache "stores" for your application as
|
|
| well as their drivers. You may even define multiple stores for the
|
|
| same cache driver to group types of items stored in your caches.
|
|
|
|
|
| Supported drivers: "array", "database", "file", "memcached",
|
|
| "redis", "dynamodb", "octane",
|
|
| "failover", "null"
|
|
|
|
|
*/
|
|
|
|
'stores' => [
|
|
|
|
'array' => [
|
|
'driver' => 'array',
|
|
'serialize' => false,
|
|
],
|
|
|
|
'database' => [
|
|
'driver' => 'database',
|
|
'connection' => env('DB_CACHE_CONNECTION'),
|
|
'table' => env('DB_CACHE_TABLE', 'cache'),
|
|
'lock_connection' => env('DB_CACHE_LOCK_CONNECTION'),
|
|
'lock_table' => env('DB_CACHE_LOCK_TABLE'),
|
|
],
|
|
|
|
'file' => [
|
|
'driver' => 'file',
|
|
'path' => storage_path('framework/cache/data'),
|
|
'lock_path' => storage_path('framework/cache/data'),
|
|
],
|
|
|
|
'memcached' => [
|
|
'driver' => 'memcached',
|
|
'persistent_id' => env('MEMCACHED_PERSISTENT_ID'),
|
|
'sasl' => [
|
|
env('MEMCACHED_USERNAME'),
|
|
env('MEMCACHED_PASSWORD'),
|
|
],
|
|
'options' => [
|
|
// Memcached::OPT_CONNECT_TIMEOUT => 2000,
|
|
],
|
|
'servers' => [
|
|
[
|
|
'host' => env('MEMCACHED_HOST', '127.0.0.1'),
|
|
'port' => env('MEMCACHED_PORT', 11211),
|
|
'weight' => 100,
|
|
],
|
|
],
|
|
],
|
|
|
|
'redis' => [
|
|
'driver' => 'redis',
|
|
'connection' => env('REDIS_CACHE_CONNECTION', 'cache'),
|
|
'lock_connection' => env('REDIS_CACHE_LOCK_CONNECTION', 'default'),
|
|
],
|
|
|
|
'dynamodb' => [
|
|
'driver' => 'dynamodb',
|
|
'key' => env('AWS_ACCESS_KEY_ID'),
|
|
'secret' => env('AWS_SECRET_ACCESS_KEY'),
|
|
'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
|
|
'table' => env('DYNAMODB_CACHE_TABLE', 'cache'),
|
|
'endpoint' => env('DYNAMODB_ENDPOINT'),
|
|
],
|
|
|
|
'octane' => [
|
|
'driver' => 'octane',
|
|
],
|
|
|
|
'failover' => [
|
|
'driver' => 'failover',
|
|
'stores' => [
|
|
'database',
|
|
'array',
|
|
],
|
|
],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Cache Key Prefix
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| When utilizing the APC, database, memcached, Redis, and DynamoDB cache
|
|
| stores, there might be other applications using the same cache. For
|
|
| that reason, you may prefix every cache key to avoid collisions.
|
|
|
|
|
*/
|
|
|
|
'prefix' => env('CACHE_PREFIX', Str::slug((string) env('APP_NAME', 'laravel')).'-cache-'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Serializable Classes
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This value determines the classes that can be unserialized from cache
|
|
| storage. By default, no PHP classes will be unserialized from your
|
|
| cache to prevent gadget chain attacks if your APP_KEY is leaked.
|
|
|
|
|
*/
|
|
|
|
'serializable_classes' => false,
|
|
|
|
];
|