mirror of
https://github.com/Part-DB/Part-DB-server.git
synced 2025-06-21 09:35:49 +02:00
Revert "Use Redis for cache on Heroku demo."
This reverts commit 4ed2f335ac
.
This commit is contained in:
parent
31a53611ac
commit
4676393818
1 changed files with 0 additions and 22 deletions
|
@ -1,22 +0,0 @@
|
||||||
framework:
|
|
||||||
cache:
|
|
||||||
# Unique name of your app: used to compute stable namespaces for cache keys.
|
|
||||||
prefix_seed: Part-DB/Part-DB
|
|
||||||
|
|
||||||
# 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: '%env(REDISCLOUD_URL)%'
|
|
||||||
|
|
||||||
# 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:
|
|
||||||
# Here all things related to cache the tree structures
|
|
||||||
tree.cache:
|
|
||||||
adapter: cache.app
|
|
||||||
tags: true
|
|
Loading…
Add table
Add a link
Reference in a new issue