Skip to main content
Bach installs the contents of exactly one folder: your program plus everything it needs next to it, such as DLLs, resources and data files. Before you write any config, find or produce that folder. This page shows what belongs in it and where common stacks put it.

What belongs in the folder

  • The .exe named by app.executable, at the top or in a subfolder.
  • Every file the program needs at run time.
  • Nothing else. Build leftovers such as *.pdb files or logs make the setup file bigger, and you can leave them out with files.exclude.
The folder is read recursively. It may not contain symbolic links, and it may not contain a file named uninstall.exe at its top, because Bach adds its own uninstaller with that name.

Typical folders per stack

bach init recognises Rust, Tauri, Electron and .NET projects and fills in the folder and the leftovers to exclude for you. See Write your bach.toml.

Runtimes your app needs

If your app needs something that is not in the folder, such as WebView2 for a Tauri app or a .NET runtime, declare it as a requirement. Setup then checks for it before installing and shows a page with a download link when it is missing.

Next step

Write your bach.toml

Describe the app and the folder in a small config file.