Skip to content

Document PATH behavior for SSH tmux sessions #1153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
radiantjade wants to merge 1 commit into from
Closed

Document PATH behavior for SSH tmux sessions #1153

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions content/docs/cli/ssh.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,19 @@ railway ssh --session debug

Railway installs tmux in the container automatically if it isn't already installed.

The tmux session starts its own shell, so it may not inherit every PATH adjustment
that appears in a direct `railway ssh` shell. For example, commands provided by
Railpack through `/mise/shims` or by local `node_modules/.bin` may be available in
`railway ssh` but missing in `railway ssh --session`. If that happens, check the
PATH inside both shells:

```bash
echo $PATH
```

Then run the command with its full path, or add the needed PATH entries to the
shell startup file used by your image so tmux shells load the same tools.

### Connect to a specific deployment instance

```bash
Expand Down
Loading