Part of the distribution-channels epic #108.
Problem
Windows users ask for winget install / choco install. Both managers only need a manifest pointing at an installer or a portable zip — the real work is producing a Windows artifact.
Proposal
Two possible artifacts, in order of preference:
- Portable zip / installer with the standalone build + bundled runtime and a
libredb-studio.cmd launcher; optionally a Windows service via WinSW or NSSM for background operation.
- Once the desktop-wrapper spike lands, its installer (MSI/NSIS from Tauri) becomes the artifact and winget/Chocolatey manifests point at that instead.
Steps for option 1:
- Produce a Windows (x64, later arm64) standalone artifact in release CI.
- Submit a winget manifest to microsoft/winget-pkgs; automate updates with wingetcreate in release CI.
- Publish a Chocolatey package (community repo) with automated pushes.
Constraints
- Native modules need Windows prebuilds; verify better-sqlite3/oracledb/mssql load on Windows.
- Code signing: unsigned binaries trigger SmartScreen; evaluate a signing certificate (or rely on winget's hash-based trust initially).
Depends on
Acceptance criteria
winget install libredb.studio (and choco install libredb-studio) installs and the launcher serves the app.
- Manifest updates are automated on release.
Part of the distribution-channels epic #108.
Problem
Windows users ask for
winget install/choco install. Both managers only need a manifest pointing at an installer or a portable zip — the real work is producing a Windows artifact.Proposal
Two possible artifacts, in order of preference:
libredb-studio.cmdlauncher; optionally a Windows service via WinSW or NSSM for background operation.Steps for option 1:
Constraints
Depends on
Acceptance criteria
winget install libredb.studio(andchoco install libredb-studio) installs and the launcher serves the app.