Skip to content

varnish: document that an activated VCL is saved to disk #525

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.

Sign up for GitHub

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

Open
dominik-matic wants to merge 2 commits into
base: master
Choose a base branch
from
+5 −3
Open

varnish: document that an activated VCL is saved to disk #525

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
db705ae
varnish: document that an activated VCL is saved to disk
Sep 16, 2026
02958c2
Merge branch 'master' into NL3WEB4-2101-vcl-persistence-docs
poespas Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The VCL you just imported and activated should have the status `active`. If all

### The "Boot" profile

To make sure your .vcl stays active even after a restart of Varnish we run a script every 5 minutes which saves the running config to /data/var/varnish/default.vcl which will be used once Varnish restarts. the "boot" profile will check what the last running .vcl was, and use that config in the "boot" profile.
To make sure your .vcl stays active even after a restart of Varnish, the running config is saved to /data/var/varnish/default.vcl as soon as a VCL is activated (and every 5 minutes as a fallback), which will be used once Varnish restarts. the "boot" profile will check what the last running .vcl was, and use that config in the "boot" profile.

This will mean that your loaded .vcl profile won't be existing the next time you'll look, and that your own .vcl profile is renamed to "boot". This is expected behaviour.

Expand Down
6 changes: 4 additions & 2 deletions docs/hypernode-platform/varnish/editing-varnish-vcl-with-hypernode-vedit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ myst:

# Editing Varnish VCL with hypernode-vedit

While we generally advise developers to make changes to the Varnish VCL in a persistent way (like `/data/web/app.vcl`), there are cases where you might want to make temporary changes directly to the active VCL. For example, when testing a change or debugging an issue.
While we generally advise developers to keep their Varnish VCL in a file of their own (like `/data/web/app.vcl`), there are cases where you might want to make quick changes directly to the active VCL. For example, when testing a change or debugging an issue.

The `hypernode-vedit` CLI tool allows you to edit the active Varnish VCL on your Hypernode. The command will store the active VCL in a temporary file, open it in the default editor, and then reload the edited VCL back into Varnish when you save and exit.

Expand All @@ -17,6 +17,8 @@ Checking VCL syntax...
Syntax OK.
Apply this VCL now? [y/N] y
VCL loaded and activated as 'vcl_1780641679'.
Waiting for the VCL to be saved to disk...
VCL saved to /data/var/varnish/default.vcl.
```

In this example, you of course don't see the actual editing process, but after you save and exit the editor, the new VCL is loaded and activated in Varnish.
In this example, you of course don't see the actual editing process, but after you save and exit the editor, the new VCL is loaded and activated in Varnish. The activated VCL is also written to `/data/var/varnish/default.vcl`, the file Varnish loads when it starts, so your change survives a restart of Varnish or of your Hypernode.
Loading