Since every page view goes through TYPO3 13, the page cache is on the hot path; TYPO3 10 kept it in Redis, TYPO3 13 had it in MySQL. Same socket and options as TYPO3 10, but databases 3-5 instead of 0-2, which may still hold TYPO3 10 entries in a format TYPO3 13 must not read. DDEV gets the redis add-on for the same setup locally. Without a Redis connection the backend logs an alert and misses, so pages still render (slower); a missing PHP redis extension, however, fails hard. Co-Authored-By: Claude Opus 5.5 <[email protected]>
13 lines
359 B
Bash
Executable File
13 lines
359 B
Bash
Executable File
#!/usr/bin/env sh
|
|
|
|
#ddev-generated
|
|
## Description: Flush all cache inside the Redis container
|
|
## Usage: redis-flush
|
|
## Example: "ddev redis-flush"
|
|
|
|
if [ -f /etc/redis/conf/security.conf ]; then
|
|
redis-cli -p 6379 -h "${REDIS_HOSTNAME:-redis}" -a redis --no-auth-warning FLUSHALL ASYNC
|
|
else
|
|
redis-cli -p 6379 -h "${REDIS_HOSTNAME:-redis}" FLUSHALL ASYNC
|
|
fi
|