aboutsummaryrefslogtreecommitdiffstats
path: root/packaging/systemd/meshbay-node.service
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-08-25 13:05:18 +0200
committerChristophe Besson <cbesson@gmail.com>2026-08-25 13:05:18 +0200
commitc52e85b984bffc78125aff744513bc5d33ad72b3 (patch)
tree2b3227b2483fb0feb981fd790d44089971c77be4 /packaging/systemd/meshbay-node.service
parent9e66c11b15b7103e963dcecf88fb152ed1e74253 (diff)
downloadmeshbay-c52e85b984bffc78125aff744513bc5d33ad72b3.tar.gz
feat(client): add app icon based on the MeshBay logo
Adds build/icon.png (1024x1024, cropped/upscaled from QE/meshbay-logo-v2.jpg) at electron-builder's default buildResources path, so packaged .deb/.rpm builds get a real icon instead of Electron's stock one. The generic `build/` gitignore rule (Python artifacts) was swallowing this legitimate source directory, so it gets an explicit exception. BrowserWindow now points at the same file for its own icon, and the process runs with --class=MeshBay so a dev run's WM_CLASS matches the StartupWMClass electron-builder derives from productName for the packaged app — kept consistent, even though the launcher/dash icon match itself only resolves once a .desktop file exists (i.e. after packaging, not in dev).
Diffstat (limited to 'packaging/systemd/meshbay-node.service')
0 files changed, 0 insertions, 0 deletions