Skip to main content
bach init writes a starter bach.toml that explains itself. In a Rust, Tauri, Wails, Electron, .NET, Flutter, PyInstaller, Qt, Godot or Unity project, it fills in the app’s name, version, publisher, program and build folder from the project’s own files.

Behaviour

  • It never overwrites. If bach.toml already exists in the folder, the command stops with a sentence saying so.
  • It prints which stack it found: Wrote bach.toml for this Rust project. Check [app] and [files], then run bach check. In an unrecognised folder it writes placeholders based on the folder’s name.
  • The file starts with the #:schema line for editor completion, and every optional setting is present as a comment.
  • In a git checkout whose origin is on GitHub, it also turns on [updates] with github = "owner/repo" for that repository. Elsewhere that section is a comment.
  • In the same GitHub checkout it also writes .github/workflows/bach-release.yml, a one-click release: see bach workflow and One-click releases. It never fails the command: if the workflow can’t be written, init says why. Without a GitHub origin it only prints a hint to run bach workflow later.

What is detected

Detection is tried in this order: Godot, Unity, Tauri, Wails, Electron, .NET, Flutter, PyInstaller, Qt, Rust.

The window’s style

init never picks a style. Whatever the project, the window starts in Bach’s own style, bach, and the starter file only shows the line as a comment:
bach.toml
To use another look, set installer.style yourself; bach styles lists them all. The starter file also shows a commented [style] section for your own fonts, colours and background.
Bach fills in what the project says about itself. Check [app] and [files] before building.
See Write your bach.toml.