> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Prepare your app: build it into one folder

> Bach installs the contents of one folder. Learn what belongs in it and which build folder to use for Rust, Tauri, Electron, .NET, Go and PyInstaller apps.

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`](/docs/reference/config/files).

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
my-app/
  bach.toml
  build/              <- [files] source
    my-app.exe        <- [app] executable
    resources/
```

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

| Stack | Typical folder |
| - | - |
| Rust | `target/release`, with `*.pdb`, `*.d`, `build/**`, `deps/**`, `incremental/**` and `.fingerprint/**` excluded. Better still, a folder you copy the `.exe` and assets into. |
| Electron (electron-builder or forge) | `dist/win-unpacked`, or `out/<name>-win32-x64` |
| Tauri | Copy `src-tauri/target/release/<app>.exe` and any resources into a folder |
| .NET | The output of `dotnet publish -c Release -r win-x64 --self-contained`, usually `bin/Release/<tfm>/win-x64/publish` |
| Go | A folder with the built `.exe` |
| PyInstaller | `dist/<name>` in one-folder mode |

> [!TIP]
>
> `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](/docs/guides/write-bach-toml.md).

## 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](/docs/guides/requirements.md). Setup then checks for it before installing and shows a page with a download link when it is missing.

## Next step

> [card] [Write your bach.toml](/docs/guides/write-bach-toml.md)
>
> Describe the app and the folder in a small config file.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.