Sync
Sync your journal to a remote server for backup and multi-device access. Sync is manual: click Sync Now to push/pull changes.
How it works
Your journal is a git repository. Sync pushes and pulls commits to/from a remote. If both sides changed since the last sync, Surebeans merges the changes. Conflicts are rare but handled with a resolution UI if they occur.
Adding a remote
- Navigate to Sync.
- Click Add Remote.
- Select a remote type and enter connection details.
- Click Sync Now to perform the first sync.
Supported remotes
| Remote | Desktop | Browser |
|---|---|---|
| GitHub | Yes | Yes |
| GitLab | Yes | Yes |
| Gitea | Yes | Yes |
| Generic Git | Yes | No |
| S3 | Yes | Yes |
| WebDAV | Yes | Yes |
| SFTP | Yes | No |
| Dropbox | Yes | Yes |
Managing remotes
- Edit: Change connection details for an existing remote.
- Delete: Remove a remote (two-stage confirmation). Does not delete remote data.
- Last sync: Timestamp of the most recent successful sync.
Conflict resolution
If a merge conflict occurs, Surebeans shows the conflicting changes side-by-side. Choose which version to keep or manually edit the result.
Browser limitations
Some remote types require native network access not available in the browser. See the table above. Git forges require CORS headers to work from the browser. By default Surebeans routes that traffic through a CORS proxy. If you self-host your forge, you can enable CORS on it and connect directly instead. See CORS for Browser Sync.