Webapp for Calaos
Web frontend for the Calaos home automation server: a
Vue 3 + TypeScript single-page app (built with Vite) that talks to
calaos_server over its WebSocket JSON API — rooms, lights, shutters,
scenarios, cameras and audio players.
Requirements: Node.js >= 22.
Develop
npm install
Fully offline, against the bundled mock calaos_server (log in with
demo / demo):
npm run mock # terminal 1 — mock calaos_server on :5454
npm run dev # terminal 2 — app on http://localhost:5173
Against a real calaos_server, create .env.development.local (gitignored,
never committed):
CALAOS_SERVER=http://192.168.1.10:5454
then npm run dev — the dev server proxies same-origin /api (WebSocket +
camera HTTP) to that host. The app itself always talks to same-origin
/api; in production it is served by calaos_server directly.
Build
npm run build
regenerates dist/. It is build output only: gitignored, never
committed — released artifacts are built by CI (see Release below).
npm run preview serves the built dist/ locally (same /api proxy rules
as dev).
Test
npm run lint
npm run typecheck
npm run test:unit # Vitest
npx playwright install chromium # once
npm run test:e2e # Playwright (builds + serves dist/, starts the mock itself)
Release
The version lives in git tags, not in package.json (which is pinned to
the placeholder 0.0.0-git). Tags are bare — no v prefix.
.github/workflows/release.yml bumps the highest existing tag with
calaos/action-bump-version:
-
Every push to master publishes a -dev.N prerelease automatically
(3.0.1 → 3.0.2-dev.0 → 3.0.2-dev.1 …). Nothing to do.
-
A real release is a manual dispatch — /release patch from Claude Code,
or by hand:
gh workflow run release.yml -f vincrement=patch # or minor / major
Either way the workflow runs every gate (test.yml as a reusable workflow),
builds the app, tags the commit, and publishes a GitHub Release whose only
asset is calaos-web-app-<version>.tar.gz — the contents of dist/,
index.html at the archive root. It creates the tag itself; never tag by hand.
It then fires a build_deb repository dispatch at
calaos/pkgdebs, which builds the
calaos-web-app Debian package from that asset and publishes it to the apt
repo at deb.calaos.fr/calaos — the normal way a Calaos system gets the app.
Consumers can also install a release by fetching the asset directly, e.g.
curl -fsSL https://github.com/calaos/calaos-web-app/releases/download/3.0.1/calaos-web-app-3.0.1.tar.gz \
| tar xz -C /path/to/webroot
