Skip to main content
A workspace is one Git repository: every folder’s content lives in it, with configuration alongside in .studiograph/. That means an owner can keep a full local checkout of the workspace and sync it with the server. This is owner-oriented tooling — day-to-day collaboration happens in the web app.

​
Clone a workspace

clone signs in with your owner email and password (via the STUDIOGRAPH_EMAIL and STUDIOGRAPH_PASSWORD environment variables), downloads the full workspace, and stores an sg_ token in ~/.studiograph/user.json so later syncs don’t need credentials.

​
Pull and push

Both commands move two things:
  • Content — entries and folder structure, transferred as Git over the server’s embedded Git endpoint at <server>/git.
  • Configuration — workspace settings such as the team name and description.
Pass --remote <url> to target a specific server and --token <token> to override the stored token (STUDIOGRAPH_TOKEN also works).

​
What doesn’t sync

The Git repository holds text content only. These live outside it and are not moved by pull/push: Back these up separately — see Storage and backups.

​
Diverged copies

If the local checkout and the server have both changed since the last sync, pull and push fail with a clear error and a non-zero exit code. Resolve the divergence manually with Git, then sync again.
If you pull into a workspace that’s currently being served, restart studiograph serve so the server picks up the new content.