Commit Graph

6 Commits

Author SHA1 Message Date
shumeiko.it
4fabed70c0 feat(desktop,launcher): default to ~/.waggle-community (P1.3c)
The Tauri shell's bundled npm environment and its first-launch flag, the
server installer's --data-dir default and the NSIS installer config
fell back to ~/.waggle. Use ~/.waggle-community (ADR-0011).

The Rust shell keeps the name in DEFAULT_DATA_DIR_NAME in lib.rs and the
launcher, which uses only Node built-ins, in DATA_DIR_NAME.
packages/shared/tests/data-dir.test.ts fails when either copy, or the
marketplace's, differs from @waggle/shared.
2026-11-04 10:31:32 +01:00
shumeiko.it
3a426a5423 feat(launcher): install the server from a prebuilt archive (P1.3c)
The launcher is now a self-contained installer with install, run, update,
doctor and uninstall. Install downloads waggle-server-<version>-<target>
.tar.gz, checks its SHA-256, unpacks it into a per-user program directory
and writes a waggle-server command that runs the tool on the archive's own
Node. Nothing is built on the user's machine and the data directory stays
WAGGLE_DATA_DIR or ~/.waggle.

scripts/build-server-archive.mjs packs the staged desktop sidecar payload
with the built web UI and a manifest. The download location waits for the
repository decision; until then install takes --from or
WAGGLE_RELEASE_BASE_URL (ADR-0009).

Removes install.sh, scripts/waggle-server.sh and their CI job, which the
installer replaces, and the bin name clash with @waggle/cli.
2026-11-01 01:35:54 +01:00
shumeiko.it
07a529512c fix(server): let the CLI server exit on Ctrl+C and SIGTERM (UF-041)
The OAuth routes started a module-level cleanup interval that was never
cleared or unref'd. The service's SIGTERM/SIGINT handler closes the server
and relies on the event loop going empty, so the process kept running: a
first Ctrl+C in `npx waggle` or `npm run dev:server` left it alive, and
SIGTERM never ended it. The interval is now unref'd.

The launcher tests left two `waggle` processes behind on every run: they
stopped `npx` but not the waggle process it started. They now start it in
its own process group and stop the whole group, with a SIGKILL fallback,
and a new test checks that the built CLI exits by itself after SIGTERM.
2026-10-25 23:01:05 +01:00
shumeiko.it
3fee3d6935 test(launcher): expect waggle.db and the memory store instead of personal.mind (P1.5) 2026-10-24 17:47:22 +02:00
Oleg Maslov
b20b138fe4 moving 2026-09-02 10:14:22 +02:00
Oleg Maslov
0c3e2ead3b moving
Some checks failed
Installer Smoke / installer-smoke (push) Has been cancelled
2026-09-02 10:10:29 +02:00