scoop install sdods gave me the app, not the sdods command — where is the CLI on Windows?

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.

Added the bucket and installed:

powershell

scoop bucket add sdods https://sdods.com/scoop
scoop install sdods

I now have a desktop application. What I wanted was sdods run in a terminal. Did I pick the wrong package name?

install windows cli

asked by Fiona McAllister

3 answers

Accepted answer
Right name, wrong channel for what you want. Scoop and winget both install the desktop app — they are the managers Windows users already have, and a GUI installer is what they are built to place.
The CLI on Windows comes from the PowerShell script or from npm:
powershell
```
irm https://sdods.com/install.ps1 | iex
```
powershell
```
npm install -g @sdods/cli
```
Both give you sdods on PATH. Having the app as well is fine — they are separate things and do not conflict.
answered by Sam Orbison
Worth reading the channel table with that split in mind: it lists three different products. The scripts, npm and Homebrew install the CLI; Docker installs the server and web UI; Scoop, winget and the Debian packages install the desktop app.
The whole table is in Getting started → Installation, with what each one needs.
answered by Daniel OyelaranSDODS team
If you install both, keep in mind that upgrading one does not upgrade the other. scoop update sdods moves the app; the CLI moves when you re-run the script or update the npm package. Ours drifted apart for a month before anyone noticed.
answered by Hsu Wei-lin

Have a different question? Ask it.

scoop install sdods gave me the app, not the sdods command — where is the CLI on Windows?

3 answers

Related