From db705ae19cf6f19c4533efcba288fb5582623b48 Mon Sep 17 00:00:00 2001 From: Dominik Matic Date: Wed, 16 Sep 2026 10:43:26 +0200 Subject: [PATCH] varnish: document that an activated VCL is saved to disk --- .../magento-2/how-to-configure-varnish-for-magento-2-x.md | 2 +- .../varnish/editing-varnish-vcl-with-hypernode-vedit.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md b/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md index 848a2bfc..e87df391 100644 --- a/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md +++ b/docs/ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md @@ -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. diff --git a/docs/hypernode-platform/varnish/editing-varnish-vcl-with-hypernode-vedit.md b/docs/hypernode-platform/varnish/editing-varnish-vcl-with-hypernode-vedit.md index d609c049..abfe59ce 100644 --- a/docs/hypernode-platform/varnish/editing-varnish-vcl-with-hypernode-vedit.md +++ b/docs/hypernode-platform/varnish/editing-varnish-vcl-with-hypernode-vedit.md @@ -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. @@ -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.