# bento-release-macos driver config.
#
# Run: bento-release-macos --config driver.toml [--version 0.4.1]
#
# Drives the macOS release on the build host's in-session ops-agent and pulls
# the signed DMG back to this machine (fw13).

[agent]
# The ops-agent's tailnet URL on the Mac build host. Must match the agent's
# `listen` address. http (not https): the tailnet (WireGuard) is the transport
# security; identity is re-checked by the agent via `tailscale whois`.
base_url   = "http://100.64.0.2:8765"
host_label = "mbp"

[plan]
app          = "goingson"
version      = "0.4.1"                  # overridable with --version
product_name = "GoingsOn"               # used for the default DMG name

# The paths below are on the BUILD HOST and must be ABSOLUTE. `~` is never
# expanded: the remote side does not expand it (repo_path is used as a step cwd,
# the rest are sh-quoted), and the driver cannot expand it either, because the
# build host's home is not this machine's (/Users/max vs /home/max). The driver
# rejects a leading `~` up front rather than failing mid-release.
repo_path    = "/Users/max/Code/Apps/goingson"   # checkout ON THE MAC
env_file     = "/Users/max/.tauri/passwords.env" # secrets sourced before the build

# Where the signed DMG lands ON THE MAC. Must match DIST_DIR in that app's
# dist/release-macos.sh, which includes a platform segment (.../<app>/macos).
# Pointing at the parent builds and notarizes fine, then fails at the verify
# step with "No such file or directory".
dist_root    = "/Users/max/Dist/goingson/macos"

# dmg_name  = "GoingsOn_0.4.1_aarch64.dmg"   # optional; default shown

[local]
# Where on THIS host (fw13) to pull the signed DMG to. This one IS on this
# machine, so a leading `~/` is expanded against your own HOME (`~user` is not).
# That is the whole difference from the `[plan]` paths above: their home is the
# Mac's, which this side cannot know, so there a `~` is rejected instead.
dest_dir = "~/Dist/goingson"