Skip to main content
The install page shows a short list of choices: where to install, optional parts of your app, and a few options like shortcuts. You control every one of them from bach.toml. This page explains the four values an option can take, what each option does, and how optional components work.

Where the app installs

bach.toml
By default the app installs to %LOCALAPPDATA%\Programs\<folder>. When the user picks another place, folder is added to it. Updates always stay where they are. A start_menu_folder is removed after uninstalling when it is empty.

The four values of an option

Each option takes one of four values: The whole row is a click target: clicking anywhere on it ticks or unticks its box. On an update, the boxes start the way the user left them last time, and unticking one takes the shortcut, PATH entry or autostart away again. With an [updates] section, the page has one more box, “Automatic updates”, ticked. Its setting is auto in [updates] and takes the same four values.
add_to_path edits only the user’s own PATH. Exactly one entry is ever added or removed, and the rest of PATH is kept byte for byte.

Optional components

Components are optional parts of your app, each shown as one box on the install page. Files that no component claims are always installed.
bach.toml
Rules:
  • A file belongs to the first component whose pattern matches it.
  • A component must match at least one file.
  • app.executable cannot be in a component.
  • Unticking a component on an update removes its files.
  • title and description can be text or a table with one text per language.
Silent installs pick components with --with samples and --without samples. See Silent installs.

Next steps

Integration

Extra shortcuts, link schemes and file types.

Reference: [installer]

All installer settings at a glance.