-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Update Cache component doc for 4.2 #11477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
d16268c
to
57c5910
Compare
92a31ac
to
c4d8431
Compare
cache.rst
Outdated
Each pool will manage a set of independent cache keys: keys of different pools | ||
never collide even if they share the same backend. This is achieved by prefixing | ||
keys with a namespace. This namespace is generated by hashing the name of the | ||
pool, the name of the compiled container class and a configurable seed that XXX HOWTO LINK TO reference/configuration/framework.rst#prefix_seed? XXX |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RST expert needed :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will take care of this tomorrow 👌🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add this to reference/configuration.framework.rst
file:
+ .. _reference-cache-prefix-seed
prefix_seed
...........
**type**: ``string`` **default**: ``null``
If defined, this value is used as part of the "namespace" generated for the
cache item keys. A common practice is to use the unique name of the application
(e.g. ``symfony.com``) because that prevents naming collisions when deploying
multiple applications into the same path (on different servers) that share the
same cache backend.
It's also useful when using `blue/green deployment`_ strategies and more
generally, when you need to abstract out the actual deployment directory (for
example, when warming caches offline).
And link it like this:
pool, the name of the compiled container class and a configurable seed that XXX HOWTO LINK TO reference/configuration/framework.rst#prefix_seed? XXX | |
pool, the name of the compiled container class and a :ref:`configurable seed <reference-cache-prefix-seed>`. |
c4d8431
to
808453a
Compare
Ok, I made some changes and hopefully added that link correctly ;). This is ready for review! |
Thank you Nicolas! |
…averryan) This PR was merged into the 4.2 branch. Discussion ---------- Update Cache component doc for 4.2 From the plane to SymfonyLive Tunis :) Fixes #9851 Commits ------- 3209040 typo 4f7b9c4 Merge branch '4.2' into cache-contracts 50736c7 clarifying d413993 tweaks b2bb888 adding anchor 67243ff proofing cache chapter updates 808453a Update Cache component doc for 4.2
From the plane to SymfonyLive Tunis :)
Fixes #9851