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.
Installer finished, green ticks all the way down, and then:
sdods: command not foundThe file is there. ls ~/.local/bin/sdods shows it and it is executable. So the install worked and something else is wrong, I just cannot see what.
Accepted answer
~/.local/bin is not on your PATH. The installer writes the command there and prints the line to add, but it does not edit your shell profile unless you ask it to.
Either add it yourself:
export PATH="$HOME/.local/bin:$PATH"or re-run the installer with --modify-path, which appends that line to your profile once:
curl -fsSL https://sdods.com/install.sh | sh -s -- --modify-pathThen open a new shell. Re-running is safe — it upgrades the install in place and the PATH line is only added once, no matter how many times you run it.
If you use zsh and you have both .zshrc and .zprofile, check which one the line landed in. Mine went into the profile and my terminal only sources .zshrc for interactive shells, so it worked in a login shell and nowhere else.
echo $PATH | tr : "\n" | grep local in the shell that fails is the quickest way to confirm which one you are in.
Same thing bit me over SSH. Non-interactive shells on our boxes read nothing at all, so a CI step that worked interactively failed in the job. Passing --bin-dir at a directory that is already on the system PATH avoids the whole question.
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.