Deployment

This guide explains how the Homepage is deployed.

Services

  • Local

  • Github

  • Cloudflare

Runtime secrets

reads selected server-only values from local and syncs them to the Cloudflare Worker before pushing the deployment package. For annotations, edit only in ; deployment uploads that value as the Worker secret of the same name.

For production cohort personalization, set and in . The project ID is added to the deployed Worker's ; the dedicated API token is synced as a server-only Worker secret. Give that token and scope. Keep the browser SDK token () separate; it is not an API token and cannot be used for cohort lookup. Local development uses and .

Quick

Terminal: All
cd ~/Development/Artificial-Colleagues/Homepage-Builder/work
make commit m="<Message>"
make deploy

Individual lines:

Terminal: Go to directory
cd ~/Development/Artificial-Colleagues/Homepage-Builder/work
Terminal: Commit current changes
make commit m="<Message>"
Terminal: Push and deploy
make deploy

Considerate

  1. Go to the directory of the Assistant:

Terminal
cd ~/Development/Artificial-Colleagues/Homepage-Builder/work

  1. Test the Homepage locally first:

Terminal
make dev

  1. Then commit all changes to Github:

Code: BASH
make commit m="<Message>"

  1. Finally deploy to Cloudflare:

Code: BASH
make deploy

  1. Check the results: