Settings

Share

Opens this same origin on another device. Does not install a native app, and does not sync notes by itself — each device keeps its own OPFS vault (Solebase) unless you configure Sync below.

  • Install / Add to Home Screen from the browser menu for an app-like icon (PWA).
  • After the first visit, the service worker + OPFS-backed Solebase vault keep the app usable offline. Losing internet ≠ losing the app once cached.
  • localhost cannot be opened usefully on a phone for E2EE — deploy over HTTPS (GitHub Pages / Cloudflare Pages / Netlify) or a TLS tunnel, then scan this QR. See docs/SHIP.md.

Solebase sync (R2)

Layer 1 Solebase.init({ sync: { provider: 's3', options } }) — E2EE changeset blobs in Cloudflare R2. Credentials stay in this browser’s localStorage only (never committed).

One dashboard step: Cloudflare dashboard → R2 → Overview → Manage API Tokens → Create → permissions Object Read & Write → apply to bucket solebase-sync-test → copy Access Key ID + Secret Access Key into the fields below. (MCP OAuth cannot mint S3 API tokens; API Tokens Write is required once.)

—

Legacy snapshot adapters

Optional older full-vault JSON sync (Drive / WebDAV / S3 object). Prefer Solebase R2 sync above for changeset E2EE.

Google Drive

Optional. Create an OAuth 2.0 Web client in Google Cloud Console. Authorized JS origin = this page’s origin. Scope: drive.appdata.

WebDAV

Recommended. Nextcloud example: https://cloud.example/remote.php/dav/files/USER/Solebase/

Legacy S3 vault object

Single encrypted JSON object (legacy). Layer 1 R2 sync uses the Solebase sync section above instead.

Backup

Manual vault export/import and legacy push/pull. Solebase Sync Now is in the R2 section.