coder-file-transferlisted

# Coder Workspace File Transfer Move large files to (or from) a Coder Cloud Development Environment reliably. The naive path — `rsync -e "coder ssh"` — is broken on macOS. Use a `coder config-ssh` host alias with a protocol-clean, PTY-free SSH channel instead. ## When to use - Uploading a directory, dataset, build artifact, or binary to a Coder workspace. - `rsync -e "coder ssh"` fails, desyncs mid-transfer, or hangs. - A copy over `coder ssh` corrupts or never completes. - You need a **resumable** transfer over a flaky dev tunnel. ## The one-liner ```bash coder config-ssh # one-time per machine rsync -avP -e "ssh -T" /local/dir <workspace>.coder:/remote/target/dir/ ``` ## Instructions 1. **Generate SSH host aliases (one-time per machine/workspace):** ```bash coder config-ssh ``` This adds host entries to `~/.ssh/config`. Note the alias for your workspace from the output — typically `<workspace>.coder` (e.g. workspace `Loom` → host `Loom.coder`). 2. **Confirm you have GNU rsync (macOS ships the incompatible `openrsync`):** ```bash rsync --version ``` If it says `openrsync`, install GNU rsync: ```bash brew install rsync ``` 3. **Ensure the remote target directory exists:** ```bash coder ssh <workspace> -- mkdir -p /remote/target/dir ``` 4. **Transfer — preferred (resumable):** ```bash rsync -avP -e "ssh -T" /local/dir <workspace>.coder:/remote/target/dir/ ``` - `-a` arch