From 1206ed716c319612950c98d410c24d7f934349fe Mon Sep 17 00:00:00 2001 From: Martin Turoci Date: Thu, 3 Aug 2023 08:55:59 +0200 Subject: [PATCH] docs: Minor update to HTTPS config. --- website/docs/deployment.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/deployment.md b/website/docs/deployment.md index 05872a5a881..99f35523982 100644 --- a/website/docs/deployment.md +++ b/website/docs/deployment.md @@ -54,6 +54,8 @@ Wave consists of 2 servers and both need to be configured separately. HTTPS is all or nothing meaning either both server and app use TLS or none does. +Once set, the Wave app needs to know it should talk to the Wave server via `https` and not `http` as it does by default. This can be set using `H2O_WAVE_ADDRESS="https://127.0.0.1:10101"` env variable when starting the Wave app. + ### Deployment to separate machines Although most people deploy their Wave server and Wave app to the same machine, it's not the only way. When deploying to separate machines, the main challenge is to make sure Wave server and Wave app can communicate properly.