Added the bucket and installed:
scoop bucket add sdods https://github.com/siri1410/scoop-sdods
scoop install sdodsI now have a desktop application. What I wanted was sdods run in a terminal. Did I pick the wrong package name?
Added the bucket and installed:
scoop bucket add sdods https://github.com/siri1410/scoop-sdods
scoop install sdodsI now have a desktop application. What I wanted was sdods run in a terminal. Did I pick the wrong package name?
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:
irm https://sdods.com/install.ps1 | iexnpm install -g @sdods/cliBoth give you sdods on PATH. Having the app as well is fine — they are separate things and do not conflict.
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.
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.
Have the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a question