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

Windows bundle: no modules either, and the read-me says where they come from

Browse Source 
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>
This commit is contained in:
Waters Church
2026-09-30 09:46:51 -04:00
co-authored by Claude Fable 5.1
parent b5d39c60dc
commit 2f14b30d68
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
launcher/windows/build.sh
+7 -3
View File
@@ -1,7 +1,8 @@
#!/bin/zsh #!/bin/zsh
# Build the Windows bundle — ProdDash-<version>-win-x64.zip: the dashboard, # Build the Windows bundle — ProdDash-<version>-win-x64.zip: the dashboard,
# its own Node runtime and a start script, so nothing has to be installed on # its own Node runtime and a start script, so nothing has to be installed on
# the Windows machine. Unzip, double-click ProdDash.bat, done. # the Windows machine. Unzip, double-click ProdDash.bat, done. It carries no
# modules: those come from the admin page's catalog into %APPDATA%\ProdDash.
# #
# ./build.sh build/ProdDash-<version>-win-x64.zip # ./build.sh build/ProdDash-<version>-win-x64.zip
# #
@@ -55,9 +56,9 @@ echo " embedding Node $NODE_VERSION (node.exe and its licence)"
unzip -q -j "$CACHE_DIR/$ZIPFILE" "$NODE_DIST/node.exe" "$NODE_DIST/LICENSE" -d "$STAGE/node" unzip -q -j "$CACHE_DIR/$ZIPFILE" "$NODE_DIST/node.exe" "$NODE_DIST/LICENSE" -d "$STAGE/node"
# ── ProdDash ───────────────────────────────────────────────────────────── # ── ProdDash ─────────────────────────────────────────────────────────────
echo " embedding ProdDash $VERSION" echo " embedding ProdDash $VERSION (no modules — the catalog installs them)"
cp "$REPO_ROOT/server.js" "$REPO_ROOT/package.json" "$STAGE/" cp "$REPO_ROOT/server.js" "$REPO_ROOT/package.json" "$STAGE/"
cp -R "$REPO_ROOT/public" "$REPO_ROOT/modules" "$STAGE/" cp -R "$REPO_ROOT/public" "$STAGE/"
# Only the checked-in defaults: config/ also holds this machine's own # Only the checked-in defaults: config/ also holds this machine's own
# modules.json and layouts when ProdDash has ever run from the checkout. # modules.json and layouts when ProdDash has ever run from the checkout.
cp "$REPO_ROOT/config/proddash.json" "$STAGE/config/" cp "$REPO_ROOT/config/proddash.json" "$STAGE/config/"
@@ -98,6 +99,9 @@ Nothing to install. This folder holds the dashboard and its own copy of Node.
3. Open http://localhost:24500 on this PC. Other devices on the network use 3. Open http://localhost:24500 on this PC. Other devices on the network use
http://<this PC's IP address>:24500. Settings are on the admin page, http://<this PC's IP address>:24500. Settings are on the admin page,
http://localhost:24500/admin. http://localhost:24500/admin.
4. The bundle ships without modules. On the admin page, tick the ones this
PC needs under Available modules and press Install selected; each one
updates on its own from then on.
Your settings and layouts live in %APPDATA%\ProdDash, not in this folder, Your settings and layouts live in %APPDATA%\ProdDash, not in this folder,
so unzipping a new version or updating never loses them. so unzipping a new version or updating never loses them.