varnish: document that an activated VCL is saved to disk - #525
Merged
Merged
Conversation
Contributor
|
Acceptance server is available at https://docs-ephs6aajr.hypernode.io. |
poespas
approved these changes
Sep 16, 2026
tdgroot
approved these changes
Sep 16, 2026
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
3 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.
The hypernode-vedit page implied the tool was for temporary changes. That was already wrong, because a cron job saves the running VCL to disk every 5 minutes. With the new varnish-vcl-saver service, an activated VCL is now written to /data/var/varnish/default.vcl immediately and the cron is left as a fallback. Mention that on the vedit page, add the new output line to its example, and drop the "every 5 minutes" wording from the Magento 2 Varnish guide.