@ibalzam/codejitsu-core 0.12.0 → 0.13.0

package/SETUP.md

@@ -393,7 +393,11 @@ npx codejitsu deploy:setup
 Interactive wizard:
 - Copies `.github/workflows/daily-deploy.yml` + `wrangler.toml` from
   package templates if missing.
-- Prompts for the Cloudflare deploy hook URL.
+- Prompts for the Cloudflare deploy hook URL(s). For a multi-site monorepo
+  (one repo → several Pages projects), enter every project's hook URL
+  comma-separated; they're stored in `CLOUDFLARE_DEPLOY_HOOK_URLS` and the
+  workflow pings each. A single site uses `CLOUDFLARE_DEPLOY_HOOK_URL`.
+  See `modules/deploy/CLAUDE.md` → "Multi-site monorepos".
 - Stores it as a GH Actions secret via `gh secret set`.
 - Optionally triggers a test run.
 

package/checklist/core.md

@@ -9,7 +9,7 @@ The runner covers the easy stuff (file presence, meta tags, canonical, schema sc
 - [ ] `npm run build` exits 0 with no warnings about missing pages, unresolved imports, or broken links.
 - [ ] `dist/` contains static HTML for every expected route. No `.html` route is missing.
 - [ ] `wrangler.toml` is present and points to `dist`.
-- [ ] `.github/workflows/daily-deploy.yml` exists; the `CLOUDFLARE_DEPLOY_HOOK_URL` secret is set in the repo (skip if site has no scheduled content).
+- [ ] `.github/workflows/daily-deploy.yml` exists; the deploy-hook secret is set in the repo — `CLOUDFLARE_DEPLOY_HOOK_URL` (single site) or `CLOUDFLARE_DEPLOY_HOOK_URLS` (comma-separated, one Deploy Hook per Pages project, for a multi-site monorepo). Skip if the site has no scheduled content.
 
 ## URLs + routing
 

package/modules/deploy/CLAUDE.md

@@ -5,7 +5,7 @@ When the user asks to **set up codejitsu/core/deploy** (or "wire up the Cloudfla
 ## What this module provides
 
 - `templates/wrangler.toml` — minimal Cloudflare Pages config.
-- `templates/daily-deploy.yml` — GitHub Action that pings a Cloudflare deploy hook every morning so scheduled blog posts (or any time-gated content) graduate from hidden to public on their publish date.
+- `templates/daily-deploy.yml` — GitHub Action that pings one or more Cloudflare deploy hooks every morning so scheduled blog posts (or any time-gated content) graduate from hidden to public on their publish date. Handles both single-site repos and multi-site monorepos (see below).
 
 ## Wiring it into a site
 
@@ -30,11 +30,34 @@ gh secret set CLOUDFLARE_DEPLOY_HOOK_URL --body "<paste URL>"
 
 Or via the GitHub UI: Settings → Secrets and variables → Actions → New repository secret, named `CLOUDFLARE_DEPLOY_HOOK_URL`.
 
+> Multi-site monorepo? Skip this step and follow **Multi-site monorepos** below instead.
+
 ### 4. Verify
 
 - Trigger the workflow manually: `gh workflow run "Daily Deploy"` (or via the GH UI).
 - A Cloudflare Pages deployment should kick off within seconds.
 
+## Multi-site monorepos
+
+A single repo can host several sites (e.g. `sites/www`, `sites/kamloops`, `sites/kelowna`), each deployed as its **own Cloudflare Pages project**. There is still only **one** `.github/workflows/daily-deploy.yml` for the repo, but it must rebuild **every** project — otherwise only one site graduates its scheduled content each morning and the rest stay stale.
+
+The template already handles this. To wire it up:
+
+1. **Create one deploy hook per Pages project** (Cloudflare dashboard → each project → Settings → Builds & deployments → Deploy hooks, branch `main`). For garagedoorpros that's three: `garagedoorpros-ca`, `gdp-kamloops`, `gdp-kelowna`.
+2. **Store all the URLs in a single plural secret, comma-separated** (one line — easiest to set and paste; Cloudflare hook URLs never contain commas):
+
+   ```bash
+   gh secret set CLOUDFLARE_DEPLOY_HOOK_URLS \
+     --body "https://api.cloudflare.com/.../www-hook,https://api.cloudflare.com/.../kamloops-hook,https://api.cloudflare.com/.../kelowna-hook"
+   ```
+
+   (Newline- or space-separated values also work — the workflow splits on commas, newlines, and spaces — but commas keep it a single line, which avoids the multi-line `--body` / paste pitfalls.)
+3. The workflow prefers `CLOUDFLARE_DEPLOY_HOOK_URLS` when present, splits it, and pings each URL. It only falls back to the singular `CLOUDFLARE_DEPLOY_HOOK_URL` when the plural secret is absent — so single-site repos need no change.
+
+**Adding a site later:** create its deploy hook, append `,<new-url>` to `CLOUDFLARE_DEPLOY_HOOK_URLS`, done. No workflow edit needed.
+
+**Verify:** `gh workflow run "Daily Deploy"` then confirm a deployment kicks off in *every* Pages project, not just one.
+
 ## Build command (for Cloudflare Pages git integration)
 
 If using Cloudflare's git integration (preferred for push-driven deploys):
@@ -45,7 +68,8 @@ If using Cloudflare's git integration (preferred for push-driven deploys):
 
 ## What must NOT be done
 
-- **Don't commit the deploy hook URL.** It belongs in `CLOUDFLARE_DEPLOY_HOOK_URL` secret only.
+- **Don't commit the deploy hook URL(s).** They belong in the `CLOUDFLARE_DEPLOY_HOOK_URL` / `CLOUDFLARE_DEPLOY_HOOK_URLS` secret only.
+- **Don't add a second daily-deploy workflow for a monorepo's extra sites.** One workflow pings all hooks via `CLOUDFLARE_DEPLOY_HOOK_URLS` — see **Multi-site monorepos**. Duplicate workflows mean duplicate crons and drift.
 - **Don't change the cron without reason.** 13:00 UTC is intentional — early-morning Pacific so posts are live by the time users wake up. If a site is on a different timezone, change it explicitly and note why in a comment in the workflow file.
 - **Don't add a `wrangler deploy` step to the cron workflow.** The workflow only *pings* the deploy hook; Cloudflare does the actual build via git integration. Doing the build twice causes drift.
 - **Don't skip the daily-deploy workflow even if the site has no scheduled content yet.** It's the safety net for when the user adds a scheduled post six months later.
@@ -54,5 +78,5 @@ If using Cloudflare's git integration (preferred for push-driven deploys):
 
 - [ ] `wrangler.toml` present at site root with correct `name`.
 - [ ] `.github/workflows/daily-deploy.yml` present.
-- [ ] `CLOUDFLARE_DEPLOY_HOOK_URL` secret set in the repo (check with `gh secret list`).
-- [ ] Cloudflare Pages project exists and is connected to the git repo.
+- [ ] Deploy-hook secret set (check with `gh secret list`): `CLOUDFLARE_DEPLOY_HOOK_URL` for a single site, or `CLOUDFLARE_DEPLOY_HOOK_URLS` (one URL per line) for a multi-site monorepo.
+- [ ] A Cloudflare Pages project exists for **each** site and is connected to the git repo, and every project has a hook in the secret.

package/modules/deploy/checklist.md

@@ -3,7 +3,7 @@
 - [ ] `wrangler.toml` exists at site root with the correct Cloudflare Pages project `name`.
 - [ ] `pages_build_output_dir = "dist"` in `wrangler.toml`.
 - [ ] `.github/workflows/daily-deploy.yml` exists and is unmodified from the template (or modifications are documented in a comment).
-- [ ] `CLOUDFLARE_DEPLOY_HOOK_URL` secret is set in the repo (`gh secret list`).
-- [ ] Cloudflare Pages project exists and is connected to the GitHub repo (git integration).
-- [ ] Pages build command is `npm run build`, output dir is `dist`, Node version is 20.
-- [ ] Manual run of `gh workflow run "Daily Deploy"` triggers a Cloudflare deployment within seconds.
+- [ ] Deploy-hook secret is set in the repo (`gh secret list`): `CLOUDFLARE_DEPLOY_HOOK_URL` (single site) or `CLOUDFLARE_DEPLOY_HOOK_URLS` (multi-site monorepo, one URL per line).
+- [ ] A Cloudflare Pages project exists for **each** site and is connected to the GitHub repo (git integration); every project's hook is in the secret.
+- [ ] Each Pages project's build command is `npm run build` (for its own site/workspace), output dir is `dist`, Node version is 20.
+- [ ] Manual run of `gh workflow run "Daily Deploy"` triggers a Cloudflare deployment in **every** Pages project within seconds.

package/modules/deploy/templates/daily-deploy.yml

@@ -3,9 +3,14 @@ name: Daily Deploy
 # Triggers a Cloudflare Pages rebuild each morning so any scheduled content
 # whose publish date has arrived graduates from hidden to public.
 #
-# Requires a repository secret named CLOUDFLARE_DEPLOY_HOOK_URL holding
-# the Deploy Hook URL from Cloudflare Pages (Project settings -> Builds &
+# Single-site repo: set the secret CLOUDFLARE_DEPLOY_HOOK_URL to the one
+# Deploy Hook URL from Cloudflare Pages (Project settings -> Builds &
 # deployments -> Deploy hooks).
+#
+# Multi-site monorepo (one repo -> several Pages projects): set the secret
+# CLOUDFLARE_DEPLOY_HOOK_URLS to ALL the projects' Deploy Hook URLs, separated
+# by commas (newlines also work). The job pings every URL so each site
+# rebuilds. If both secrets are set, the plural one wins.
 
 on:
   schedule:
@@ -18,12 +23,23 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
-      - name: Ping Cloudflare deploy hook
+      - name: Ping Cloudflare deploy hook(s)
         env:
+          HOOKS: ${{ secrets.CLOUDFLARE_DEPLOY_HOOK_URLS }}
           HOOK: ${{ secrets.CLOUDFLARE_DEPLOY_HOOK_URL }}
         run: |
-          if [ -z "$HOOK" ]; then
-            echo "CLOUDFLARE_DEPLOY_HOOK_URL secret is not set"
+          # Prefer the plural (multi-URL) secret; fall back to the singular one.
+          urls="$HOOKS"
+          [ -z "$urls" ] && urls="$HOOK"
+          if [ -z "$urls" ]; then
+            echo "Neither CLOUDFLARE_DEPLOY_HOOK_URLS nor CLOUDFLARE_DEPLOY_HOOK_URL is set"
             exit 1
           fi
-          curl --fail-with-body -X POST "$HOOK"
+          # Accept commas, newlines, or spaces as separators between URLs.
+          failed=0
+          for url in $(echo "$urls" | tr ',\n' '  '); do
+            [ -z "$url" ] && continue
+            echo "Pinging deploy hook: ${url%%\?*}"
+            curl --fail-with-body -X POST "$url" || failed=1
+          done
+          exit $failed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ibalzam/codejitsu-core",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "type": "module",
   "description": "Shared core for Codejitsu Astro sites — reusable code and Claude-facing instructions for blog, SEO, images, deploy, and llms.txt.",
   "keywords": [