Skip to main content
A profile is another build of the same app from the same bach.toml. Each profile holds only what differs from the file above it.
bach.toml
Anything else in a profile is a section of bach.toml, laid over the main file. A table is merged key by key; an array (like [[components]]) is replaced as a whole. A profile can’t change config_version or contain profiles. A profile’s name is lowercase letters, digits and -, up to 32 characters.
  • A ZIP holds the files of the components ticked by default, with a fixed date on every entry, so the same files give the same ZIP. It can’t be locked with [access] and has no window to preview.
  • A setup profile shares app.id with the main build unless it sets another. Give a profile that must live next to the main build its own app.id and installer.folder. Profile builds never write the update feed.
  • With --msi, a setup profile also writes its own MSI.