Repository navigation
[Docs] Clarify that the Docker Redis service is not used by the cache by default - #615
Open
berfinyuksel wants to merge 1 commit into
Open
berfinyuksel wants to merge 1 commit into
berfinyuksel wants to merge 1 commit into
Conversation
… by default The Installation page tells readers to configure Redis as the cache backend, and both Docker packages start a Redis-compatible service, but neither package wires Pimcore's object cache to it: the cache pool config in config/config.yaml is commented out and defaults to the database adapter. - Installation README: say explicitly that the service is started but the cache pool must be enabled, and link to the Docker-specific steps. - Skeleton Installation: add an "Enabling the Redis cache" section with REDIS_URL, config/packages/cache.yaml, and cache:clear / cache:warming, and point out that inside Docker the host is `redis`, not `localhost`. - Demo Enterprise Installation: note that the `valkey` service and the existing REDIS_URL are not used by the cache until enabled. Co-Authored-By: Claude <noreply@anthropic.com>
berfinyuksel
added
the
Skip Milestone Check
fashxp
requested changes
Oct 13, 2026
fashxp
left a comment
fashxp
left a comment
Member
There was a problem hiding this comment.
I'd rather change demo and skeleton repos so that we don't need that doc adaptions...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Installation page says "configure a caching backend … Redis is the recommended cache adapter", and both Docker packages start a Redis-compatible service — but neither package actually wires Pimcore's object cache to it. The
pimcore.cache.poolblock inconfig/config.yamlis commented out (and usesredis://localhost, which doesn't resolve inside Compose), so a fresh install silently runs on the database adapter (cache_items).Changes
REDIS_URL=redis://redis:6379in.env.local,config/packages/cache.yaml(same pool config as the Performance Guide),cache:clear+pimcore:cache:warming, and a note that the host inside Docker isredis, notlocalhost.valkeyservice / existingREDIS_URLare not used by the cache until enabled.Verification
pimcore/skeleton@2026.xandpimcore/demo-enterprise@2026.x: Redis is only referenced in the commented block ofconfig/config.yaml(andREDIS_URLin the demo.env); noconfig/packages/*file configures the pool.#enabling-the-redis-cache,#pimcore-caching-redis.🤖 Generated with Claude Code