Files
crm_ecosplay/config/packages/cache.yaml
Serreau Jovann a9057374d4 fix: deplacer le pool dns_infra_cache dans le bon fichier cache.yaml
config/packages/cache.yaml:
- Ajout du pool dns_infra_cache avec adapter cache.app et TTL 3600s
- Le pool etait dans config/packages/packages/cache.yaml qui est
  surcharge par config/packages/cache.yaml, donc le service
  dns_infra_cache n'existait pas

config/packages/packages/cache.yaml:
- Suppression du pool dns_infra_cache (doublon)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-02 22:17:29 +02:00

22 lines
751 B
YAML

framework:
cache:
# Unique name of your app: used to compute stable namespaces for cache keys.
#prefix_seed: your_vendor_name/app_name
# The "app" cache stores to the filesystem by default.
# The data in this cache should persist between deploys.
# Other options include:
# Redis
#app: cache.adapter.redis
#default_redis_provider: redis://localhost
# APCu (not recommended with heavy random-write workloads as memory fragmentation can cause perf issues)
#app: cache.adapter.apcu
# Namespaced pools use the above "app" backend by default
pools:
dns_infra_cache:
adapter: cache.app
default_lifetime: 3600