Kaleta 2.9.0

Kaleta 2.9 is about many sites as one: a fleet console that shows all your Kaleta sites on one screen, sorted by what needs attention, with staged updates – plus a monthly report e-mail for each site's owner. Separate installations, never multisite.

Fleet console

Switch on the Fleet console extension on one Kaleta installation – your agency's, for example. It becomes the console of your other sites.

• Pairing: on the console, Fleet → Add a site makes a one-time pairing key (24 hours). Paste it on the site in Settings → Fleet console.
• Reports: every site sends the console a signed report every hour – version, health, background jobs, backups, updates, enquiries waiting, visits and site-audit findings. Counts and states only, never names, e-mail addresses or the content of enquiries.
• One screen: the sites that need attention come first – a site that does not answer, stopped reporting, has errors, a failed update, failing background jobs or no recent backup. Each site has a detail page with its last report.
• Uptime: the console asks each site's home page every 5 minutes. A site that does not answer twice in a row, or stops reporting for a day, is an event – and the alert e-mail tells you.
• The console cannot get into the sites. Each site has its own key pair and signs its reports; the console signs its answers. The site always calls the console, never the other way round, and the console holds no password or token for any site.

Staged updates

A site can let the console decide when new versions install (Settings → Fleet console, on by default when pairing).

• Test sites (choose them on the console) get a new version at once.
• The rest get it once every test site has run it for 48 hours without errors, without being down and without a failed update. Without test sites, 48 hours after the console first saw the version.
• Security releases go to every site at once.
• Allow the new version everywhere now skips the wait. Sites install an allowed version within an hour.
• Only versions signed by the Kaleta publisher install, and every update still checks itself afterwards and undoes itself when the site stops working (2.8).

Monthly report by e-mail

Settings → Mail → Monthly report (off by default): on the first of each month the site e-mails a short report about the previous month – visits and the top pages, sources and campaigns, enquiries and newsletter sign-ups, updates and backups, changes made by people and by Claude, and what needs a decision. With the agency's name, logo and contact when they are set (Settings → General). Preview last month shows the e-mail first.

Claude

On a console, list_sites lists the sites that report to it, the ones needing attention first, and get_site shows a site's last report. Both only read – Claude changes a site through that site's own connection.

Fixed

• Automatic security updates now really install themselves when they are switched on in Backups and updates. The background job that should have run them was never connected.
• Alert e-mails (2.8) are in the site's language; they were sent in English.

Updating

Update from Settings → Backups and updates. It works from every earlier release. This release adds two tables for the console; the update creates them.