Push → PDF Chain

What the chain looks like

There are 4 pieces that need to talk to each other for a user to subscribe and unlock PDFs.

Each piece runs in a different runtime — browser, Cloudflare edge, Cloudflare KV, and Node.js. They are connected only through HTTP calls and a shared KV namespace. No tool currently traces the full chain automatically.

BUG Subscribe button in PDF modal did nothing

ELI5: Imagine a vending machine with a "pay here" button, but the payment reader is turned off. You press the button, nothing happens. That's what was happening — the subscribe button called window.PushSubscribe.subscribe(), but PushSubscribe was never loaded because push was disabled.

FIXED Enable pushNotify in bookpost AppCoreConfig

What happens when a user clicks the PDF button

1. 1
   PDF button clicked

   User taps the little printer icon in the toolbar.

   onclick="handlePrintClick()"

   bookpost.html:1412 — button element bookpost.html:1724 — handlePrintClick()
2. 2
   Access check

   The code asks: "Does this person have a VIP pass?" It checks localStorage for the key push_subscribed=1. If yes → go straight to PDF. If no → show the modal.

   _hasPdfAccess() → checks localStorage.getItem('push_subscribed') === '1'

   bookpost.html:1605 — _hasPdfAccess() bookpost.html:1597 — _isPushSubscribed()
3. 3
   Modal opens (no access)

   If no VIP pass, a popup appears saying "subscribe to push notifications to get the PDF."

   _onPdfProtected('push-required') → _showPdfPrompt()

   bookpost.html:1642 — _showPdfPrompt() bookpost.html:1473 — modal HTML element
4. 4
   User clicks subscribe in modal

   The big button in the popup. Calls window.PushSubscribe.subscribe() — this is the function from push_subscribe.js. If that script isn't loaded (old bug), nothing happens.

   handlePdfSubscribeClick() → window.PushSubscribe.subscribe()

   bookpost.html:1670 — handlePdfSubscribeClick() push_subscribe.js — PushSubscribe module
5. 5
   Browser asks for notification permission

   The browser shows its own system dialog: "Allow notifications from this site?" If user says yes, the browser gives us a unique subscription token.

   Notification.requestPermission() → reg.pushManager.subscribe(...)

   push_subscribe.js — subscribe() method
6. 6
   Subscription token sent to Cloudflare Worker

   We POST the token to our Cloudflare Worker. Think of it like mailing your address to a magazine — so they know where to deliver.

   _sendToBackend(sub) → POST https://push-gate.techiediaries.workers.dev/subscribe

   push_subscribe.js — _sendToBackend() worker.js:158 — /subscribe handler
7. 7
   Worker saves subscriber to KV

   The Worker writes the subscription + your country, city, timezone into a Cloudflare KV database. It's like a notebook with entries per subscriber.

   Stores: endpoint, keys, country, city, timezone, ua, timestamp

   worker.js:167 — entry object built worker.js:182 — KV.put()
8. 8
   localStorage key set + PDF unlocks

   Back in the browser, we stamp push_subscribed=1 in localStorage (the "VIP pass"). Then handlePrintClick() runs again — this time _hasPdfAccess() returns true and the PDF opens.

   localStorage.setItem('push_subscribed', '1') → document.dispatchEvent('pushSubscribed') → handlePrintClick() retries

   push_subscribe.js — sets push_subscribed bookpost.html:1695 — closePdfPromptModal + retry bookpost.html:1752 — pushSubscribed event listener

Checking subscribers from the terminal

The CLI reads the same KV via the Worker's /stats endpoint. Run:

Things not done yet

TODO Per-site tracking — subscribers from ahmedbouchefra.com and techiediaries.com share the same KV with no way to tell them apart. The worker doesn't save which site the subscription came from.

TODO Per-app subpath subscriptions — users can't subscribe to just one app (e.g. /techquiz). It's all-or-nothing.

TODO Cross-runtime chain tracing — no tool currently maps the full browser → worker → KV → CLI chain as a navigable graph. Options: explicit chains.json, extend codeknow with HTTP contract edges, or an architecture doc.