RTOpacks Launch Cutover Procedure¶
Last updated: 5 April 2026
How traffic routing works (current state)¶
| Pattern | Worker | Purpose |
|---|---|---|
| rtopacks.com.au/* | rtopacks-prelaunch | Holding page — blocks all apex traffic |
| www.rtopacks.com.au/* | rtopacks-prelaunch | Same holding page |
| staging.rtopacks.com.au/* | rtopacks-site | Real site (CF Access protected) |
The rtopacks-site Worker has custom domain entries for rtopacks.com.au and www.rtopacks.com.au in its wrangler.jsonc. These are currently dormant because Cloudflare route-based Workers take priority over custom domains.
What goes live when you delete the prelaunch routes¶
Deleting the two rtopacks-prelaunch routes causes rtopacks-site custom domains to take over immediately. rtopacks.com.au and www.rtopacks.com.au will serve the real site. There is no DNS change required.
Cutover procedure (when ready to launch)¶
Step 1 — Pre-launch checklist¶
- CF Access policy removed from staging.rtopacks.com.au (or kept — up to Tim)
- PERF-02 warmer verified hitting staging URL (already fixed — confirm still active)
- Search returning results (resultCount > 0 — verify)
- StatBar data live (confirm stats-cache cron active)
- All open mop-up items closed or consciously deferred
Step 2 — Remove prelaunch routes (THE switch)¶
In Cloudflare dashboard → Workers & Pages → rtopacks-prelaunch → Routes: - Delete: rtopacks.com.au/ - Delete: www.rtopacks.com.au/
Do NOT delete the rtopacks-prelaunch Worker itself — keep it as a rollback option.
Step 3 — Verify¶
curl -I https://rtopacks.com.au
# Expect: HTTP 200, x-worker: rtopacks-site (not prelaunch)
curl -I https://www.rtopacks.com.au
# Same
Step 4 — Rollback (if needed)¶
Re-add the two routes to rtopacks-prelaunch in CF dashboard. Takes effect immediately. No deployment required.
Important¶
- Do NOT run
wrangler delete --name rtopacks-prelaunchuntil well after launch - Do NOT modify wrangler.jsonc custom domains — they are correctly configured
- The switch is the route deletion only — nothing else changes