Vizoalica v0.7.3 — Fewer values to install, one place to choose where you are

Deployment support: no D1 schema change and no backend change. A backend deployed with 0.7.0 to 0.7.2 needs nothing: the console and the Worker match on 0.7. Snippets, workflow variables and configuration files from earlier versions keep working unchanged.

Installing a website takes fewer values

• The recommended snippet is three attributes: src, data-endpoint and data-source. The token path (/vizoalica/ingest-token), consent (unknown) and project (taken from the source key) are defaults, and the script location is site-relative, so it is right on every hostname. Everything can still be written out under "Customize the snippet". data-token-url="none" sends unsigned events, for demos only.
• The GitHub → Cloudflare Pages path takes one VIZOALICA_SITE variable, the two Cloudflare values and the two secrets: five values instead of twelve. The site folder defaults to the repository root. The separate variables still work and win over the bundled one. The starter workflow now points at v0.7.3.
• "I've deployed, check now" runs a check that names the one thing to fix: SDK file, token endpoint, allowed origin, a redirect to an address you have not allowed, or the configuration file. It looks at every allowed address, never follows a redirect itself, and asks your token endpoint for a token that it discards unread (it expires in five minutes); the page says so next to the button.

If you upgrade an existing site

Nothing breaks. One default changed meaning: a snippet without data-token-url used to send unsigned events, and now asks /vizoalica/ingest-token for a signed token. If that path is missing the events are still sent, unsigned, as before. To keep sending unsigned on purpose (a demo), write data-token-url="none".

Adding and managing websites

• Add a website by pasting its address as you copied it; the console shows the exact origin it will save, offers the www counterpart, and names the website after its domain. The project is the one chosen at the top.
• After an edit, the console says whether your installed site needs a change (a new origin list does; a new name does not). Deleting says what the live tag will do.

One place to choose where you are

• The environment and the project sit together at the top of every page except Projects. The environment control no longer overlaps its text and shows the role and any problem separately. The project menu only switches; projects are created and deleted on the Projects page.
• The footer is one line. The console version is on the Health page.
• Backend is now the first section of Health (its old address opens Health). Projects and Access keys leave the sidebar; Access keys is reached from a website's Share section and the environment menu, for administrators.

Access keys you can use

The Access keys page has role and access dropdowns that explain each choice, a website picker (by name), inline errors, and a list that shows what each key reaches. After you issue a key it says what to do with it: nothing to deploy, and how the recipient adds a console environment for this backend in a private file, with OneCLI, or from a script. See Environments.

Fixed

The install check (and the reachability check behind it) asked the Worker for a record it does not serve, so on a deployed backend it answered "not found". It now works; it was found by testing against a real backend.

Install or update

npm install -g vizoalica      # or: npm update -g vizoalica
vizoalica --version           # 0.7.3