Interactive Development
This guide walks through using Chaser as a persistent remote development environment with a real shell, file persistence, and port forwarding.
Set up a workspace
Create a named workspace so your files persist across sessions:
Optionally pin an OCI image for a custom base environment:
Boot and connect
Your shell drops you into /workspace where workspace files are mounted.
Run a dev server with port forwarding
Start a server inside the sandbox and access it locally:
This binds http://127.0.0.1:8080 and proxies traffic to port 3000 in the sandbox. You can also access it directly at https://<session_id>.chaser.sh/forward/3000/.
Upload project files
Push local files to the sandbox:
Snapshot before risky changes
Create a restore point before a major upgrade:
If something goes wrong, restore:
Clone a workspace for branches
Create an independent copy of your workspace for parallel work:
Import from GitHub
Import a repository directly into a new workspace:
The repository is cloned into /workspace and the repo selector is saved on the workspace for re-bootstrap.
Related
- Sandbox Sessions — shell, exec, and file access
- Port Forwarding — local and direct forwarding
- Workspaces — snapshots, templates, cloning
