-
-
Notifications
You must be signed in to change notification settings - Fork 149
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
1. Your usage scenarios?
I use the install.sh script in Coder workspaces, where only the current user's home directory (~) is persisted across workspace restarts.
System-wide directories (e.g., /usr/local/bin) are ephemeral and get reset after a workspace restart—this means tools installed to these paths are lost, forcing me to re-run the install script every time the workspace restarts.
Installing to ~/.local/bin (a standard user-local binary directory in the persisted home directory) would ensure the tool remains available after workspace restarts, but the current script only supports system-wide installation (requiring sudo/root and installing to non-persistent paths).
2. What is your expected outcome?
- Add a
--userflag toinstall.sh. When used (e.g.,./install.sh --user):- The script installs the binary to
~/.local/bin(automatically create the directory if it does not exist). - Bypass sudo/root permission checks (since
~/.local/binis within the user's writable home directory). - Ensure
~/.local/binis added to the user's$PATH(if not already present) to make the tool accessible immediately.
- The script installs the binary to
- Keep the default behavior (install to system-wide paths like
/usr/local/bin) when--useris not specified (preserve backward compatibility).
Copilot
Metadata
Metadata
Labels
enhancementNew feature or requestNew feature or request