frommeandClaude Opus 5.5
df3d823de4
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]>
28 lines
705 B
YAML
28 lines
705 B
YAML
#ddev-generated
|
|
services:
|
|
redis:
|
|
container_name: ddev-${DDEV_SITENAME}-redis
|
|
image: ${REDIS_DOCKER_IMAGE:-redis:8}
|
|
hostname: ${REDIS_HOSTNAME:-redis}
|
|
# These labels ensure this service is discoverable by ddev.
|
|
labels:
|
|
com.ddev.site-name: ${DDEV_SITENAME}
|
|
com.ddev.approot: ${DDEV_APPROOT}
|
|
restart: "no"
|
|
expose:
|
|
- 6379
|
|
volumes:
|
|
- ".:/mnt/ddev_config"
|
|
- "ddev-global-cache:/mnt/ddev-global-cache"
|
|
- "./redis:/etc/redis/conf"
|
|
- "redis:/data"
|
|
command: /etc/redis/conf/redis.conf
|
|
x-ddev:
|
|
describe-url-port: |
|
|
Backend: ${REDIS_DOCKER_IMAGE:-redis:8}
|
|
describe-info: |
|
|
Pass: <none>
|
|
|
|
volumes:
|
|
redis:
|