Bernd Rodler
cab43b8d06
Phase 1 step 7 of VNCprodbuild. electron/main.ts calls autoUpdater.checkForUpdatesAndNotify() once the app is ready, only for packaged builds (app.isPackaged) - dev/test runs have no latest.yml and would just log a noisy 404 on every launch. electron-builder.config.js gets a matching `publish` block pointing at this repo's own GitHub Releases (brvncde-dotcom/vncmail-plus) - the skill's recommendation over standing up a new distribution channel, since the repo is already private. Flagged as the "light decision" the skill calls it, not blocking. Deliberately defensive: no code signing yet (step 9), so update verification can fail on macOS in particular. Wrapped in try/catch + autoUpdater's "error" event so a failed check is logged and swallowed, never fatal - this is background maintenance, not something the user should be blocked on. Verified with a --dir packaged build: checkForUpdatesAndNotify() throws ENOENT for app-update.yml (expected - that file is only emitted by a full `electron-builder build`, not --dir) and the error handling swallows it cleanly; the standalone server still boots and serves the app normally. npm run test:electron still green (4/4) - autoUpdater is a no-op in the unpacked dev/test path this suite exercises.
95 lines
4.3 KiB
JavaScript
95 lines
4.3 KiB
JavaScript
// electron-builder config for the VNCmail+ (Bulwark) desktop shell.
|
|
//
|
|
// Phase 1 of the VNCprodbuild rollout (~/.claude/skills/VNCprodbuild/SKILL.md):
|
|
// step 1 - base config, no targets (superseded by this file)
|
|
// step 6 - this file: real packaging targets + branding icon (below)
|
|
// step 7 - this file's `publish` block + electron/main.ts's
|
|
// setupAutoUpdater() - electron-updater against GitHub Releases.
|
|
// step 9 - still open: code signing / notarization (Apple Developer ID,
|
|
// optional Windows cert) - both are human-owned purchases, not
|
|
// configured here. Builds below ship UNSIGNED.
|
|
module.exports = {
|
|
appId: "de.vnc.vncmailplus",
|
|
productName: "VNCmail+",
|
|
copyright: "Copyright © VNC AG",
|
|
directories: {
|
|
output: "dist-electron-builds",
|
|
},
|
|
files: ["dist-electron/**/*", "package.json"],
|
|
extraResources: [
|
|
{
|
|
// Same artifact the Dockerfile bakes into the container image (see
|
|
// Dockerfile + scripts/assemble-standalone.mjs). electron/main.ts
|
|
// reads it from process.resourcesPath in packaged builds.
|
|
//
|
|
// Deliberately `from: ".next"` (not ".next/standalone") + a filter,
|
|
// not the more obvious `from: ".next/standalone"` alone:
|
|
// app-builder-lib's copy filter unconditionally drops a directory
|
|
// literally named "node_modules" sitting at the copy root (see
|
|
// node_modules/app-builder-lib/out/util/filter.js's
|
|
// `relative === "node_modules"` check - it assumes extraResources are
|
|
// hand-authored assets, not a pre-built server with a traced
|
|
// node_modules of its own). Copying from one level up so
|
|
// "standalone/node_modules" is never the literal copy root sidesteps
|
|
// that check, so the standalone server's node_modules actually
|
|
// survives into the packaged app instead of getting silently
|
|
// stripped (caught by manually launching a --dir build - the packaged
|
|
// server crashed with "Cannot find module 'next'").
|
|
from: ".next",
|
|
filter: ["standalone/**/*"],
|
|
to: ".",
|
|
},
|
|
],
|
|
// STAND-IN ICON, not a dedicated app icon: public/icon-512x512.png is the
|
|
// PWA manifest icon (512x512 square PNG). electron-builder can generate
|
|
// .icns/.ico from a single square PNG at build time (see
|
|
// node_modules/app-builder-lib/out/util/iconConverter.js), so this
|
|
// produces working icons for every target below - but at only 512x512,
|
|
// the largest macOS icns representation (1024x1024 "ICON512@2x") gets
|
|
// upsampled and will look soft compared to a real 1024x1024+ source.
|
|
// public/branding/Bulwark_Icon_App.svg looks like the intended master for
|
|
// this (as opposed to Bulwark_Favicon.png, sized for browser tabs), but
|
|
// it's vector and this environment has no SVG rasterizer (rsvg-convert /
|
|
// ImageMagick / Inkscape) to turn it into a proper 1024x1024 PNG. A human
|
|
// (or a follow-up step with the right tooling) should export
|
|
// Bulwark_Icon_App.svg at 1024x1024 and point `icon` at that instead.
|
|
icon: "public/icon-512x512.png",
|
|
mac: {
|
|
target: [
|
|
{ target: "dmg", arch: ["x64", "arm64"] },
|
|
{ target: "zip", arch: ["x64", "arm64"] },
|
|
],
|
|
category: "public.app-category.productivity",
|
|
// No Apple Developer ID yet (VNCprodbuild step 9) - ship unsigned/
|
|
// un-notarized for now. hardenedRuntime is meaningless without signing
|
|
// but left explicit so it's obvious what step 9 needs to flip on.
|
|
hardenedRuntime: false,
|
|
},
|
|
win: {
|
|
target: [{ target: "nsis", arch: ["x64"] }],
|
|
},
|
|
nsis: {
|
|
oneClick: false,
|
|
allowToChangeInstallationDirectory: true,
|
|
},
|
|
linux: {
|
|
target: [
|
|
{ target: "AppImage", arch: ["x64"] },
|
|
{ target: "deb", arch: ["x64"] },
|
|
],
|
|
category: "Network;Email;",
|
|
},
|
|
// electron-updater feed (see electron/main.ts's setupAutoUpdater()).
|
|
// GitHub Releases, not a new distribution channel - the skill's
|
|
// recommendation since this repo is already private and this needs no
|
|
// extra infrastructure. "Light decision" per VNCprodbuild step 7, not
|
|
// blocking, but flagged: switching later (e.g. to a self-hosted update
|
|
// server) would mean revisiting this block and the `provider` electron-
|
|
// updater talks to.
|
|
publish: {
|
|
provider: "github",
|
|
owner: "brvncde-dotcom",
|
|
repo: "vncmail-plus",
|
|
},
|
|
};
|