v1.0.38
init sets up your first-party proxy key
Points clés
- When
zenovay initwrites a first-party proxy for Cloudflare Pages, it now also creates the site's proxy key. The key proves to Zenovay that requests really come from your proxy, so nobody can send fake visitor locations through it.initshows the key once, with the exact place to add it: Cloudflare dashboard > Workers & Pages > your project > Settings > Variables and Secrets > Add, asZENOVAY_PROXY_KEY. - If
wrangleris installed and logged in,initoffers to store the key as an encrypted Pages secret for you. The key is never written to a file in your project.
Corrections
- A new key does nothing until your proxy sends it for the first time, so creating one can never cost you data. If the site already has a key,
initleaves it alone and tells you where to replace it. - In headless runs (
--json, CI, or output that is not a terminal)initdoes not create a key, because that output usually ends up in logs. It points to Domain settings instead. zenovay sessions: the page column now shows the pages a session viewed (it showed the replay's internal event count, labelled "events").- The bounce-rate alert example now uses a percent threshold (70), matching how alerts are evaluated.