From 3ff3883061ec4fe037ff2dcc84f6063da620b53b Mon Sep 17 00:00:00 2001 From: "P. Douglas Reeder" Date: Tue, 26 Nov 2024 13:47:13 -0500 Subject: [PATCH] Notes that NODE_COOKIE, GUARDIAN_KEY, & PHX_KEY should be changed --- community-edition/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community-edition/readme.md b/community-edition/readme.md index 72b091b..765dea8 100644 --- a/community-edition/readme.md +++ b/community-edition/readme.md @@ -44,7 +44,7 @@ Before applying the configuration file to your Kubernetes cluster, you will need To deploy to your K8s cluster on your chosen hosting solution, follow these steps: -- In `input-values.yaml` edit `HUB_DOMAIN`, `ADM_EMAIL`, `SMTP_SERVER`, `SMTP_PORT`, `SMTP_USER`, `SMTP_PASS` and optionally `SKETCHFAB_API_KEY` with the values for your site. +- In `input-values.yaml` edit `HUB_DOMAIN`, `ADM_EMAIL`, `SMTP_SERVER`, `SMTP_PORT`, `SMTP_USER`, `SMTP_PASS` and optionally `SKETCHFAB_API_KEY` with the values for your site. Change `NODE_COOKIE`, `GUARDIAN_KEY`, & `PHX_KEY` to unique random values, using a password generator if you have one handy. - Run `npm run gen-hcce && npm run apply` to generate your configuration in `hcce.yaml` and apply it to your K8s cluster. From the output read your load balancer's external IP address. - Expose the services - On your DNS service, create four A-records to route your domains to the external IP address of your load balancer