Skip to content

Commit

Permalink
Notes that NODE_COOKIE, GUARDIAN_KEY, & PHX_KEY should be changed
Browse files Browse the repository at this point in the history
  • Loading branch information
DougReeder committed Nov 26, 2024
1 parent cd595a8 commit 3ff3883
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion community-edition/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 3ff3883

Please sign in to comment.