From f566695d55b3e101c9bb78513652357df1aba8a4 Mon Sep 17 00:00:00 2001 From: Martijn Eichelsheim Date: Wed, 8 Apr 2026 15:29:36 +0200 Subject: [PATCH] Improve storecode usage for Hypernodes running behind firewall On hypernodes behind a firewall, we dont have varnish.storecode. storecodes and configuration should be configured in server.storecode instead. --- .../nginx/how-to-configure-nginx-for-a-multistore.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md b/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md index e8637cfc..9754af9a 100644 --- a/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md +++ b/docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md @@ -37,9 +37,9 @@ set $storecode "example_storecode"; ``` ```{important} -If you have a multistore, with hypernode-manage-vhost enabled AND you are using Varnish. -You'd have to prefix the file with `varnish` instead of `server`, like `varnish.storecode`. -This way these multistore requests will go through varnish and will then be rewritten accordingly with the `varnish.storecode` configuration. +If you have a multistore with `hypernode-manage-vhost` enabled **and** you are using Varnish, you need to prefix the file with `varnish` instead of `server`, like `varnish.storecode`. This way multistore requests will go through Varnish and be rewritten accordingly using the `varnish.storecode` configuration. + +This does **not** apply if your Hypernode is running behind a load balancer (e.g. a cluster setup). In that case, you should keep using `server.storecode` instead. ``` ### Use a different Store Type