Skip to content

Improve storecode usage for Hypernodes running behind firewall #468

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

Merged
martijneichelsheim merged 1 commit into from
Apr 8, 2026
+3 −3
Merged

Improve storecode usage for Hypernodes running behind firewall #468

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions docs/hypernode-platform/nginx/how-to-configure-nginx-for-a-multistore.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading