Set up your booking calendar

Setting up needs a GitHub account and a Cloudflare account, both free — use existing ones or create new ones; the wizard guides either way. Nothing is installed on your computer and you need no server of your own: your own calendar is the only storage.

This wizard keeps track of where you are and highlights the next needed action — read ahead and come back freely. If you close the page midflight, the wizard may lose some detail: done steps stay done, but a few values are asked again. It re-checks the world every twenty seconds; the Check again button asks at once. Every outside page opens in one work window beside this one — the first step below sets the two up. SETUP.md holds the why behind every step. At the “Store the configuration” step, below, your passwords and API keys are sealed in this browser and stored, encrypted, in your own copy of the project on GitHub, for your deploys to hand to your own services — no server of this project ever sees them, for there is none.

1. Instructions in this window, every outside page in one work window beside it.
2. Two free accounts — GitHub hosts your page, Cloudflare runs the API.
3. Your own copy of the project on GitHub — one click.

   GitHub Username Fork name Everything else — the Worker's address, your page's URL — the wizard discovers from the deploy itself.
4. Where your OPEN hours live and where bookings are written.
5. A token that lets the deploy publish the booking API.
6. The Brevo key and the address your confirmations come from.
7. How your OPEN blocks are cut into bookable slots.
8. One token paste — everything lands encrypted in your fork.

   The knobs are remembered by this browser; passwords, keys and tokens stay in this tab's memory until you write them to your fork — close the tab and you will need to paste them again.
9. One switch so GitHub may publish your booking page.
10. One button — GitHub builds and ships both halves.
11. The API checks its own wiring and reports back.
12. Records at your domain so confirmation emails get delivered.
13. An OPEN event in your calendar: the time customers may book.
14. Book, get the email, cancel — the whole loop, once.

1. The Google account your calendar is in — and Google Cloud, opened once.
2. A Cloud project of your own — any name will do.
3. Two APIs switched on — one for your bookings, one for these checks.
4. The account your booking API signs in as, and its key file.
5. One key file, dropped or pasted — Google says whether it takes it.
6. Your calendars, shared with the service account.
7. Back to the main list, with everything Google needs.

   Back