Vizoalica v0.7.0 — Install from npm and manage multiple environments

Install 0.7.2. 0.7.0 and 0.7.1 were released on GitHub but could not be published to npm; v0.7.2 is the same release with the package build and its release check fixed.

Deployment support: no D1 schema change for an existing backend. This release is about how the console is installed and how it finds the backends you work with; the Worker and its database contract are unchanged.

Compatibility: the console's local settings move to one file, ~/.config/vizoalica/environments.json, managed with vizoalica env. The layout of the in-development build never shipped and is not read.

Vizoalica 0.7.0 changes how the console is installed and how it knows which backend to talk to, without changing what it collects or reports.

Install and run the console from npm — no source checkout. npm install -g vizoalica then vizoalica console.

Environments, managed outside the console. vizoalica env list | add | update | remove | check manages the backends you work with (dev, stage, prod, or any names). They live in one file you can edit, ~/.config/vizoalica/environments.json. Each has its own Worker address (a workers.dev address or your own custom domain), role (admin, owner, or analyst), and secret, in the file or held by OneCLI as a local vault, plus an optional Cloudflare token for admins. Every environment is verified against its Worker, including that the credential really has the chosen role.

A welcome page, and a picker. If no environment is usable, the console says what is wrong with each and which vizoalica env command fixes it. Otherwise it opens on the environment you used last, and the top bar switches between them.

Create a backend and replace its secrets from the terminal. vizoalica env add NAME asks whether to deploy a new backend (vizoalica deploy) or connect to one that exists, explaining each question. The generated secrets are shown last and the command waits until you type saved. vizoalica rotate NAME token (or admin, digest, all) replaces a secret on the Worker. Add --verbose to any command to see each step, never a secret.

Not in this release. The console no longer deploys or updates a backend, rotates secrets, or purges deleted data. Create a backend with vizoalica deploy <name> --apply, rotate with vizoalica rotate, and update one with pnpm vizoalica backend from a source checkout.

Upgrading

1. If you run Vizoalica from a source checkout, your pnpm vizoalica commands keep working. To use the npm-installed console, npm install -g vizoalica, then add each backend with vizoalica env add NAME (the Worker address, your role, and the secret; OneCLI users add --secret-onecli).
2. Environments are not migrated: this release changes where and how they are stored, and the earlier layout never shipped. See Environments.