Skip to content

Commit f566695

Browse files
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.
1 parent 17f4ce4 commit f566695

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ set $storecode "example_storecode";
3737
```
3838

3939
```{important}
40-
If you have a multistore, with hypernode-manage-vhost enabled AND you are using Varnish.
41-
You'd have to prefix the file with `varnish` instead of `server`, like `varnish.storecode`.
42-
This way these multistore requests will go through varnish and will then be rewritten accordingly with the `varnish.storecode` configuration.
40+
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.
41+
42+
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.
4343
```
4444

4545
### Use a different Store Type

0 commit comments

Comments
 (0)