The old UI was a single 200-line Go file serving one hand-written HTML page of task rows. It showed that archied was running and almost nothing about what it was doing -- skills, workflows, memory, channels, logs and configuration were all invisible unless you read the source or the config file. The dashboard now covers each of those as its own section, built as a Vite app under ui/ at the repo root: it is a separate artefact from the Go daemon, not an internal package of it. dist/ is committed so building archied never needs a Node toolchain, and the !no_ui build tag keeps an embed-free build available. Both sides are split by concern rather than by layer -- one Go file per API area, one folder per UI section with its own CSS -- so a change to logs cannot disturb tasks. Pages report consequences, not just state: an empty memory page says Archie starts every conversation with no recollection of earlier ones, and the setup checklist names what is missing in plain language instead of showing a grid of zeroes. Nothing greets by a hardcoded name; the operator comes from [chat], which is deployment data. Auth is exposure control, not capability control -- the agent already holds this user's authority through its own tools. So a loopback bind needs no token, and only a reachable bind mints one and logs a URL, which means an instance cannot be exposed merely by omitting config. Container startup now degrades instead of aborting, for the reason resolveForge already does: a missing agent image should not deny the operator chat and the dashboard, and under Restart=on-failure it turns a recoverable problem into a crash loop with the real error scrolling past. `task dev` runs the daemon under air and the Vite server together in one terminal.
29 lines
898 B
JavaScript
29 lines
898 B
JavaScript
import { defineConfig } from "vite";
|
|
|
|
// The dashboard is served from the archied binary, so the build output is a
|
|
// committed dist/ that ui/embed.go embeds. Hashed asset names are avoided:
|
|
// dist/ lives in git, and hashed filenames would leave a new orphan on every
|
|
// rebuild rather than overwriting the previous one.
|
|
export default defineConfig({
|
|
base: "./",
|
|
build: {
|
|
outDir: "dist",
|
|
emptyOutDir: true,
|
|
rollupOptions: {
|
|
output: {
|
|
entryFileNames: "assets/[name].js",
|
|
chunkFileNames: "assets/[name].js",
|
|
assetFileNames: "assets/[name].[ext]",
|
|
},
|
|
},
|
|
},
|
|
server: {
|
|
// `npm run dev` proxies the API to a locally running archied so the
|
|
// dashboard can be developed without rebuilding the Go binary.
|
|
proxy: {
|
|
"/api": "http://127.0.0.1:8484",
|
|
"/events": { target: "http://127.0.0.1:8484", ws: true },
|
|
},
|
|
},
|
|
});
|