From 075784dfe065c7338f00601af51b5a6531299b8c Mon Sep 17 00:00:00 2001 From: Tim Veluwenkamp Date: Tue, 16 Sep 2025 11:50:48 +0200 Subject: [PATCH 1/2] Update how-to-configure-nginx-for-a-multistore.md Make the varnish note a warning so it is more visible and less likely to be skipped --- .../nginx/how-to-configure-nginx-for-a-multistore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ca382be1..60438452 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 @@ -36,7 +36,7 @@ When you opt for using different domains for each storefront then it will be rel set $storecode "example_storecode"; ``` -```{note} +```{warning} 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. From c1de27ae9e4275fde6e70d739578169c4c61c062 Mon Sep 17 00:00:00 2001 From: Jonathan Date: Tue, 16 Sep 2025 12:18:08 +0200 Subject: [PATCH 2/2] Update docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md --- .../nginx/how-to-configure-nginx-for-a-multistore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 60438452..e8637cfc 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 @@ -36,7 +36,7 @@ When you opt for using different domains for each storefront then it will be rel set $storecode "example_storecode"; ``` -```{warning} +```{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.