Uninstall
Each route removes what it put there, and none of them touch your identity, trust material, config or state.
First, the services — before the binaries
If this machine was set up to come back after a restart — the setup page does that by default once the machine is admitted — its supervisor holds units whose command lines name the very binaries the commands below delete. Remove the units first, or the supervisor is left starting a target that is gone, on every boot or login, with nothing left on disk to explain it:
Machine-wide, both take --system, and uninstall needs sudo:
Run it in the same scope the install used; each scope holds its own units, and services registered
by another installation are never touched. See saphan service.
Then, the binaries
Per-user install:
Machine-wide install from the one-line installer:
System-wide package:
macOS self-extracting installer:
A central server placed by hand (Central servers) is not
removed by any of these, because no delivery route put it there. Stop it before you delete
it — saphan-oauth by the SIGTERM its own document describes — and then remove the file
wherever you put it.
Apart from the binaries, none of these touch ~/.saphan (or /opt/saphan) or your workspace —
your identity, trust material, configuration and state survive an uninstall, and are yours to
remove separately if that is what you want.