Fleet console: all your sites on one screen.

What it is

The fleet console is an ordinary Kaleta installation – your agency's site, for example – with the Fleet console extension switched on (Extensions). Your other Kaleta sites report to it, and it shows all of them on one screen. Every site stays a separate installation with its own database and administration.

Pair a site

1. On the console: Fleet → Add a site. The console shows a pairing key – valid for 24 hours and only once.
2. On the site: Settings → Fleet console, paste the key and click Pair.
3. The site sends its first report right away; from then on every hour.

Both sides show the fingerprints of their keys, so you can compare them. Disconnect from the console on the site ends the pairing on both sides.

What a site reports

Version, health, background jobs, the last backup, updates, enquiries waiting for an answer, visits in the last 7 days and site-audit findings. Counts and states only – never names, e-mail addresses or the content of enquiries.

What needs attention

The list starts with the sites that need you: a site that does not answer, has stopped reporting, has errors, a failed update, failing background jobs or no recent backup; then warnings, cron that is not set up, enquiries waiting and new versions. Each site has a detail page with its last report and the problems it reports.

The console checks every 5 minutes that each site's home page answers. A site that does not answer twice in a row, or has not reported for a day, is recorded as an event – the console's alert e-mail tells you (System status → Alerts).

Staged updates

When a site lets the console decide (the checkbox when pairing, or later in Settings → Fleet console):

• Test sites – mark them in the site's detail 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.

A site installs an allowed version within an hour. Only versions signed by the Kaleta publisher install, and each update checks itself and undoes itself when the site stops working.

Security

Every 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: the console cannot send a site commands and holds no password or token for any site. The most it can do is allow a signed update the site would install anyway.

Claude

Connect Claude to the console and ask what needs attention: list_sites lists the sites, get_site shows a site's last report. Both only read. To change something on a site, Claude uses that site's own connection.

Monthly report for the site's owner

Each site can e-mail its owner a short report about the previous month – visits, enquiries, sources, updates, backups, changes and what needs a decision – with your agency's name, logo and contact. Switch it on in Settings → Mail → Monthly report; Preview last month shows the e-mail first.