Transfer files

Prerequisites

Sign in with rig login on your machine, which sets up SSH access, and start the workspace. Work from your own terminal. The examples use a workspace named my-project; rig workspace ssh-info --workspace my-project shows the alias for yours.

Copy files

scp, sftp, and rsync accept the workspace alias:

scp ./notes.txt my-project:/home/developer/notes.txt
scp my-project:/home/developer/notes.txt ./notes.downloaded.txt
rsync -av ./project/ my-project:/home/developer/project/

Run sftp my-project for an interactive session. Editors that open remote files over SFTP can use the same alias. Compare the downloaded file with the original. If permissions fail, choose a path owned by the workspace user rather than a system or managed release directory. Use a development directory for manually copied source; incremental app releases manage their own directories. Use local deployment when the goal is to update an app rather than transfer working files.

Without the managed SSH config

If you turned off automatic SSH setup, use the full target instead of the alias. With jq installed:

TARGET=$(rig workspace ssh-info --workspace WORKSPACE --output json | jq -r .ssh_target)
scp ./notes.txt "$TARGET:/home/developer/notes.txt"

Start here

Deploy applications

Configure applications

Workspaces and storage

AI and tools

Operate and troubleshoot

Examples

CLI reference

Build on Rigbox

Prerequisites

Copy files

Without the managed SSH config

​Prerequisites

​Copy files

​Without the managed SSH config

Prerequisites

Copy files

Without the managed SSH config