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.tomlalready 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
#:schemaline for editor completion, and every optional setting is present as a comment. - In a git checkout whose
originis on GitHub, it also turns on[updates]withgithub = "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: seebach workflowand One-click releases. It never fails the command: if the workflow can’t be written,initsays why. Without a GitHuboriginit only prints a hint to runbach workflowlater.
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
installer.style yourself; bach styles lists them all. The starter file also shows a commented [style] section for your own fonts, colours and background.
See Write your bach.toml.