Ripple
All guides

Team workspaces

File-based collaboration on disk — no Ripple-hosted cloud. Share collections via OneDrive, NAS, or Git with optional local secret overrides.

Jump to section

Personal vs workspace

Switch modes from the workspace switcher at the top of the Collections sidebar. Personal and workspace data are fully separate — nothing is deleted when you switch.

ModeStorageUse for
Personal (default)ripple.db on your machineSolo API testing, history, cookies, chat
WorkspaceFolder you choose on diskTeam-shared collections and environments

Create a workspace

Suggested folder locations

  • Mixed / business — shared OneDrive or SharePoint folder
  • On-prem — \\fileserver\api-team\ripple-workspace
  • Developers — local folder inside a Git clone
  • Click + Workspace in the sidebar switcher
  • Enter a name (e.g. Payments API Team)
  • Pick an empty folder — OneDrive, SharePoint, NAS, or a Git clone
  • Ripple scaffolds the workspace and switches you into workspace mode

Import from personal

While in workspace mode, click Import in the switcher to copy from your personal library:

Non-secret variables (e.g. baseUrl) are written into the workspace default environment. Secrets get placeholders in shared files; teammates set their own values or use .ripple/secrets.local.json on each machine.

  • Whole collection — pick the exact collection name
  • Individual requests — comma-separated personal request IDs
  • Import always copies — personal ripple.db is never modified

Collaborate with teammates

Git (optional)

  • Init — git init + .gitignore (excludes secrets and conflicts)
  • Pull / Commit / Push — standard Git workflow on the workspace folder
  • Use a private GitLab/GitHub repo or self-hosted Gitea
  • Place the workspace folder in a shared location (OneDrive, NAS, etc.)
  • Each teammate opens the same folder path via Open workspace…
  • Edits save to files; Ripple polls for external changes (~3s) and reloads

Secrets (Postman-style)

LayerFileSynced?
Shared env valuesenvironments/*.jsonYes (via your sync transport)
Local secret overrides.ripple/secrets.local.jsonNo — per machine, gitignored

Conflict handling

If two people edit the same request file simultaneously, Ripple uses last-writer-wins and keeps a backup in .ripple/conflicts/ for recovery.

What stays personal

  • Request history
  • Cookies
  • Chat / Son of Anton sessions
  • Personal global variables (unless imported)

rip CLI with workspaces

  • rip --workspace ~/team-workspace collections list
  • rip --workspace ~/team-workspace run collection payments-api --environment default
  • rip --workspace ~/team-workspace workspace info
  • rip --workspace ~/team-workspace env show default

Troubleshooting

IssueFix
Teammate doesn't see changesConfirm sync finished (OneDrive icon, git pull)
{{apiToken}} unresolvedSet secret in workspace env or local secrets file
Wrong env values after importImport uses your active personal environment only