From 4676393818b45162d2ab1f03d96d892bc2a4006c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6hmer?= <jan.h.boehmer@gmx.de>
Date: Mon, 30 Mar 2020 00:21:55 +0200
Subject: [PATCH] Revert "Use Redis for cache on Heroku demo."

This reverts commit 4ed2f335ac64db5a5ecb68323869dbe1d0ff80e6.
---
 config/packages/demo/cache.yaml | 22 ----------------------
 1 file changed, 22 deletions(-)
 delete mode 100644 config/packages/demo/cache.yaml

diff --git a/config/packages/demo/cache.yaml b/config/packages/demo/cache.yaml
deleted file mode 100644
index a4fe3bf9..00000000
--- a/config/packages/demo/cache.yaml
+++ /dev/null
@@ -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