Vizoalica v0.9.1: Access keys page, easier deploys
Deployment support: no database migration. The backend (Worker) changed: key rename and rotate endpoints. Update a running backend with vizoalica deploy <name> --update, or all of them with vizoalica deploy --update --all.
On top of v0.9.0:
- Access keys page. A website's page has an Access keys card and button that open a full page listing keys by name and role (admin, website owner, analyst), with Create, Rename, Rotate, and Delete. The built-in Admin key is listed and cannot be deleted there, so deleting keys never locks you out. Key values are shown only once, at creation. This replaces Share setup.
- Ingestion endpoint on the website page. The Details card shows it with a copy button.
- Version in the console. The footer shows
Vizoalica vX.Y.Z, and the backend version when it differs. - Sign in to Cloudflare in your browser.
vizoalica env addandvizoalica deployoffer browser sign-in (default) or a pasted API token with a pre-filled token link.--cloudflare-loginskips the question. vizoalica deploy --update --allupdates every environment you administer, stopping at the first failure.- One vocabulary in the console, CLI, README, and docs: project ID, website ID, website key, ingestion endpoint, backend address, token endpoint, admin key, access key.
- Fixed: from a source checkout,
deployandenv addnow build the Worker files and database changes on every run instead of shipping whatever was built last. The npm README and homepage no longer describe the removed "save two secrets" step. - Security: dependency updates, including
@modelcontextprotocol/sdk1.32.1 (GHSA-6qxp-vccf-f47h) andsource-map-js1.2.2 (GHSA-68fv-2mgg-jv7q).
Install or update
sh
npm install -g vizoalica # or: npm update -g vizoalica
vizoalica --version # 0.9.1
vizoalica deploy --update --all