aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing/setup-testing-env.sh
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-09 10:21:36 -0500
committerCraig Jennings <c@cjennings.net>2026-05-09 10:21:36 -0500
commitf3dc2a905e4328d6fc16aa15d091ec65edcfc120 (patch)
treeefa7f2678787db43e387968b1bfab72883c9497d /scripts/testing/setup-testing-env.sh
parent1b58db366885bf014d14da19d14da8ee68aff9da (diff)
downloadarchsetup-f3dc2a905e4328d6fc16aa15d091ec65edcfc120.tar.gz
archsetup-f3dc2a905e4328d6fc16aa15d091ec65edcfc120.zip
feat: add post-install cmail Bridge setup
Bridge first-run is interactive, so I put the cmail wiring in a post-install helper rather than running it inside archsetup. scripts/cmail-setup-finish.sh handles the post-first-run steps idempotently: it decrypts the encrypted cmailpass, copies Bridge's self-signed cert to ~/.config/protonbridge.pem, symlinks the cmail-action triage helper into ~/.local/bin, and enables the user-level protonmail-bridge service. I added loginctl enable-linger in essential_services so the user service survives logout — without it, triaging cmail from a remote agent or SSH session has nothing to talk to. outro prints a four-step runbook for the manual steps after reboot.
Diffstat (limited to 'scripts/testing/setup-testing-env.sh')
0 files changed, 0 insertions, 0 deletions