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.
This commit is contained in:
@@ -809,7 +809,9 @@ describe('Tauri Production Configuration', () => {
|
||||
sharp: '0.35.3',
|
||||
});
|
||||
|
||||
const fastifyStaticRanges = ['launcher', 'server'].map((workspace) => {
|
||||
// The installer (packages/launcher) ships no server dependencies: it
|
||||
// downloads the staged sidecar payload instead.
|
||||
const fastifyStaticRanges = ['server'].map((workspace) => {
|
||||
const workspaceManifest = JSON.parse(fs.readFileSync(
|
||||
path.join(ROOT, 'packages', workspace, 'package.json'),
|
||||
'utf-8',
|
||||
@@ -820,7 +822,6 @@ describe('Tauri Production Configuration', () => {
|
||||
|
||||
const betterSqliteRanges = [
|
||||
'core',
|
||||
'launcher',
|
||||
'marketplace',
|
||||
'server',
|
||||
].map((workspace) => {
|
||||
|
||||
Reference in New Issue
Block a user