Bead archie-core-8cda.5.5: - task dev now runs archie-ui (dev:dashboard) on :8484 -- after the cutover archied binds no dashboard listener, and Vite's /api,/events proxy needs a live receiver there. dev:mobile starts archie-ui with a LAN bind and -token-file (reusing the pre-cutover token path) instead of a mobile archied overlay; dev:ui's summary points at archie-ui. - deployments/dev.toml documents itself as the archie-ui overlay and states the [services.gateway] target explicitly. - systemd-user-service.md: the auth gap is now the documented posture -- archie-ui has no secret registry, resolves GATEWAY_TOKEN/ STATE_STORE_TOKEN from its process environment only, so the starter (EnvironmentFile) exports them; worked env-file example added, plus /healthz as the token-free liveness probe. - INSTRUCTIONS.md ships five binaries with archie-ui in the quickstart and the token story; README.md carries the auth note; the docker-nats-stack profile notes archie-ui binds [web] and dials the same [services.*] targets. - release tooling: archied's component closure extends with cmd/archie-ui and internal/app/archieui, so a UI-process-only commit can no longer fall between the two changelogs; RELEASING.md documents that the UI Service ships inside the archied release.
33 lines
1.1 KiB
JavaScript
33 lines
1.1 KiB
JavaScript
import { defineConfig } from "vite";
|
|
import preact from "@preact/preset-vite";
|
|
|
|
// The dashboard is served from the archie-ui binary (and, for the snapshot
|
|
// renderer only, still linked by archied), 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({
|
|
plugins: [preact()],
|
|
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 archie-ui (the
|
|
// process that serves the dashboard after the UI cutover) 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 },
|
|
},
|
|
},
|
|
});
|