Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Managed laptop. The question I have to answer in writing is not "is it safe", it is "what does it touch" — specifically whether it edits my shell profile, whether it puts anything in a system directory, and whether removing it later is a matter of deleting one tree or hunting for leftovers.
I have read the script and I think the answer is "no, almost nothing", but I would rather quote something than paraphrase myself to a reviewer.
Accepted answer
There is a table for exactly this, and it is short. On a default install:
sdods command, a two-line shim that execs the real one--browsers noneEverything else is behind a flag you have to type: the shell profile only with --modify-path, a workspace only with --workspace, a source checkout only with --source git, an agent client config only with --mcp. Nothing is written to a system directory unless you point --bin-dir at one.
The full version, including what each path is for, is in Reference → Installer. That is the page to attach to the request.
If the reviewer would rather see it from your machine than from our docs, the script will tell them itself. --dry-run prints every step it would take and writes nothing:
curl -fsSLO https://sdods.com/install.sh
sh install.sh --dry-run --browsers chromium
And --version-check prints the paths it resolved on this specific machine, then exits:
sh install.sh --version-check
Between the two, a reviewer gets the claim and the evidence for it without anyone having to trust a summary.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.