michael/ProdDash
1
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases 1 Wiki Activity

Release builds: Intel disk images, a Windows bundle, and where to download them #24

Merged
michael merged 4 commits from claude/release-builds into main 2026-09-30 09:58:13 -04:00
Conversation 0 Commits 4 Files Changed 5
+160 -5
michael commented 2026-09-24 17:54:01 -04:00
Owner
Copy Link
Copy Source

Why

Nothing about ProdDash was downloadable: the README told people to "open the disk image", but no image had ever been published, and the only Windows path was a checkout plus a Node install. This is the build tooling and the documentation for packaged releases — 1.10.0 is the first one, already built from this branch and pushed to michael/ProdDash-releases.

What — build scripts and docs only; no server or module code

  • launcher/macos/build.sh takes ARCH=x86_64 for Intel Macs. The Swift target and the embedded Node follow (nodejs.org calls that build darwin-x64; the script maps it). Default unchanged: arm64. The DMG is named ProdDash-<version>-x86_64.dmg. Carries main's 1.10.0 change: no modules in the payload, no Swift helper compile.
  • launcher/windows/build.sh is new (and executable). The shell alone — server.js, public/, the shipped config/proddash.json, no modules — plus node.exe from nodejs.org, checksum-verified against its SHASUMS256.txt, and ProdDash.bat, which sets PRODDASH_LAUNCHER=1 and loops on exit code 75, so the admin page's update restarts the server the way the macOS launcher does. A README.txt in the zip covers first run, the firewall prompt, %APPDATA%\ProdDash, installing modules from Admin, starting with Windows and updates. Output: build/ProdDash-<version>-win-x64.zip. No Windows launcher app yet — this is a portable bundle.
  • README "Run it" points at the Releases page and the ProdDash-releases repo that holds the files, with a line each for Apple silicon, Intel and Windows; the launcher README shows the Intel invocation; .gitignore covers the new build output and cache.

Merging changes nothing on a running install: package.json is untouched, so the booths' update check (versions only for archive installs) sees nothing new.

Verified

  • ./build.sh --notarize and ARCH=x86_64 ./build.sh --notarize from this branch merged with main: ProdDash-1.10.0-arm64.dmg and ProdDash-1.10.0-x86_64.dmg, launcher and Node of the right architecture, signatures verify, Apple notarisation Accepted, stapled; payload holds config, package.json, public, server.js — no modules/.
  • launcher/windows/build.sh run on 2026-09-30: Node fetched and checksum-verified, ProdDash-1.10.0-win-x64.zip (34 MB) with node/node.exe, ProdDash.bat (CRLF), README.txt, and no modules/ entries.
  • All three downloaded anonymously from ProdDash-releases and their SHA-256 match the builds.

🤖 Generated with Claude Code

## Why Nothing about ProdDash was downloadable: the README told people to "open the disk image", but no image had ever been published, and the only Windows path was a checkout plus a Node install. This is the build tooling and the documentation for packaged releases — **1.10.0** is the first one, already built from this branch and pushed to `michael/ProdDash-releases`. ## What — build scripts and docs only; no server or module code - **`launcher/macos/build.sh` takes `ARCH=x86_64`** for Intel Macs. The Swift target and the embedded Node follow (nodejs.org calls that build `darwin-x64`; the script maps it). Default unchanged: arm64. The DMG is named `ProdDash-<version>-x86_64.dmg`. Carries main's 1.10.0 change: no modules in the payload, no Swift helper compile. - **`launcher/windows/build.sh` is new** (and executable). The shell alone — `server.js`, `public/`, the shipped `config/proddash.json`, no modules — plus `node.exe` from nodejs.org, checksum-verified against its `SHASUMS256.txt`, and **`ProdDash.bat`**, which sets `PRODDASH_LAUNCHER=1` and loops on exit code 75, so the admin page's update restarts the server the way the macOS launcher does. A `README.txt` in the zip covers first run, the firewall prompt, `%APPDATA%\ProdDash`, installing modules from Admin, starting with Windows and updates. Output: `build/ProdDash-<version>-win-x64.zip`. No Windows launcher app yet — this is a portable bundle. - **README "Run it"** points at the Releases page and the `ProdDash-releases` repo that holds the files, with a line each for Apple silicon, Intel and Windows; the launcher README shows the Intel invocation; `.gitignore` covers the new build output and cache. Merging changes nothing on a running install: `package.json` is untouched, so the booths' update check (versions only for archive installs) sees nothing new. ## Verified - `./build.sh --notarize` and `ARCH=x86_64 ./build.sh --notarize` from this branch merged with main: `ProdDash-1.10.0-arm64.dmg` and `ProdDash-1.10.0-x86_64.dmg`, launcher and Node of the right architecture, signatures verify, Apple notarisation **Accepted**, stapled; payload holds `config`, `package.json`, `public`, `server.js` — no `modules/`. - `launcher/windows/build.sh` run on 2026-09-30: Node fetched and checksum-verified, `ProdDash-1.10.0-win-x64.zip` (34 MB) with `node/node.exe`, `ProdDash.bat` (CRLF), `README.txt`, and no `modules/` entries. - All three downloaded anonymously from `ProdDash-releases` and their SHA-256 match the builds. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
michael added 1 commit 2026-09-24 17:54:02 -04:00
Release builds: Intel disk images, a Windows bundle, and where to download them b5c539ba05 
launcher/macos/build.sh takes ARCH=x86_64 for Intel Macs — the Swift target
and the embedded Node follow (nodejs.org calls that one darwin-x64). The
default stays arm64.

launcher/windows/build.sh is new: the same payload plus Node for Windows,
checksum-verified against nodejs.org, and ProdDash.bat, which keeps the
server running and starts it again on exit code 75 — the admin page's update
restart — the way the macOS launcher does. No Windows launcher app yet.

The README's Run it section now points at the Releases page and the
ProdDash-releases repo that holds the files, one line each for Apple
silicon, Intel and Windows.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
michael added 2 commits 2026-09-30 09:47:02 -04:00
Merge remote-tracking branch 'origin/main' into claude/release-builds b5d39c60dc
Windows bundle: no modules either, and the read-me says where they come from 2f14b30d68 
The same change the Mac build got in 1.10.0: the bundle carries the shell
alone; the admin page's catalog installs modules into %APPDATA%\ProdDash.
README.txt gains the step.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
michael added 1 commit 2026-09-30 09:55:00 -04:00
Windows build script: executable, like the Mac one c6a44e6ddc 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
michael merged commit c11389473f into main 2026-09-30 09:58:13 -04:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
chris christian michael (Michael McGary)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: michael/ProdDash#24