Skip to main content
This quickstart takes you from an app on your disk to a Setup.exe you can share. It needs the bach command, a folder that holds your built app, and about five minutes.
1

Install Bach

You do not need Rust, and nothing asks for administrator rights. With Node.js 18 or newer, on Windows, macOS or Linux:
Then check the install:
No Node.js? In PowerShell, one line installs bach.exe and bach-setup.exe to %LOCALAPPDATA%\Programs\bach-cli and adds that folder to your PATH (open a new terminal afterwards):
For macOS or Linux without Node.js, a zip download or a Scoop install, see Install Bach.
2

Build your app into one folder

Bach installs the contents of one folder. Build or copy your app into it, with the .exe and everything it needs next to it: DLLs, assets, data files.
See Prepare your app for typical folders per stack.
3

Write bach.toml

In your project folder, run:
In a Rust, Tauri, Electron or .NET project, bach init fills in the name, version, publisher, program and build folder from the project’s own files. Otherwise it writes placeholders for you to edit. Only two sections are required:
bach.toml
4

Check the config

bach check lists every file the installer will install, or tells you in one sentence what is wrong, naming the setting at fault.
5

Preview the window

This opens the real installer window with every step pretended. Nothing is installed. Add --uninstall to see the removal window, --theme dark for dark mode and --lang de for another language. Preview needs Windows.
6

Build

The setup file lands in dist\My App-Setup-1.0.0.exe by default. Run it to try the real thing, then remove the app again from Settings › Apps.
You now have a single Setup.exe that installs your app for the current user, adds a Start menu shortcut and registers an uninstaller.

Make it yours

All of these are optional:
bach.toml

Release from GitHub with one click

In a GitHub repository, bach init also wrote .github/workflows/bach-release.yml (bach workflow adds it to an existing project). Commit and push it, then press Actions › Release › Run workflow. It raises the version in every file that has one, builds your app and the setup file, and publishes a release that installed apps update from. See One-click releases.

Ship an update by hand

Raise version in bach.toml, rebuild, and hand out the new setup file. Running it over an install updates it in place: it keeps the folder and the user’s choices, and removes files the new version no longer ships. If anything goes wrong midway, the earlier version stays exactly as it was.
Keep [app] id (it defaults to the name) the same across versions. It is how Bach recognises an existing install, and changing it makes updates install side by side.

Next steps

Customize the window

Logo, accent, theme, languages, license and every text.

Sign your setup file

Reduce SmartScreen warnings with a code-signing certificate.

Updates

Update over older installs, or let the installed app update itself.

Automate in CI

Build the setup file with the GitHub Action or any pipeline.