Skip to content

docs: use explicit ~/.cargo/bin path for post-cargo-install sudo#10

Merged
niklasfrick merged 1 commit into
mainfrom
docs/cargo-install-explicit-path
Apr 22, 2026
Merged

docs: use explicit ~/.cargo/bin path for post-cargo-install sudo#10
niklasfrick merged 1 commit into
mainfrom
docs/cargo-install-explicit-path

Conversation

@niklasfrick
Copy link
Copy Markdown
Owner

Summary

  • The command -v spark-dashboard form from docs: use absolute path for post-cargo-install sudo command #9 fails when ~/.cargo/bin isn't on the user's interactive PATH (e.g. distro-packaged cargo rather than rustup) — it expands to empty and sudo errors with sudo: : command not found
  • Switch to the unambiguous sudo ~/.cargo/bin/spark-dashboard service install form in Quick Start, Option A, and the Upgrade section
  • Updated the explanatory note accordingly

Test plan

  • Fresh host with distro cargo (no rustup PATH): cargo install spark-dashboard && sudo ~/.cargo/bin/spark-dashboard service install succeeds
  • Fresh host with rustup: same command still works
  • Upgrade path: cargo install --force spark-dashboard && sudo ~/.cargo/bin/spark-dashboard service install succeeds

command -v fails when ~/.cargo/bin is not on the user's interactive PATH
(e.g. distro-packaged cargo rather than rustup). The absolute path form
works regardless of how Rust was installed.
@niklasfrick niklasfrick merged commit ee235a1 into main Apr 22, 2026
5 checks passed
@niklasfrick niklasfrick deleted the docs/cargo-install-explicit-path branch April 22, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant