Remote Sync

Lore can sync your local database with a remote Turso or LibSQL instance, giving you backups and multi-device access.

Supported Platforms

Connect

Interactive

lore remote connect

Prompts for platform, URL, and auth token.

Non-interactive

lore remote connect --platform turso --url https://mydb-myorg.turso.io --token <token>

Connection settings are saved to ~/.lore/config.json. Tokens are stored separately in ~/.lore/credentials.json with restricted permissions.

Push

Send local commits to the remote:

lore push

Push reads all local commits after the remote’s HEAD and sends them sequentially. If the remote has commits you don’t have locally, push fails with SYNC_NON_FAST_FORWARD — run lore pull first.

Pull

Fetch remote commits to your local database:

lore pull

Pull finds the common ancestor between local and remote histories, then fetches and replays all remote commits after that point. Each replayed commit is fully hash-verified.

If the histories have diverged with no common ancestor, pull fails with SYNC_DIVERGED.

Sync

Pull then push in one command:

lore sync

Clone

Set up a new local database from a remote:

lore clone <url> --platform <turso|libsql> [--force-new]

This creates a fresh local database, saves the remote configuration, and pulls all commits. Use --force-new to overwrite an existing local database.

Auto-Sync

After every lore apply, Lore automatically attempts to push if a remote is configured. Errors are handled silently — auto-sync won’t interrupt your workflow.

Sync State

Check the sync status:

lore remote status

The sync state is one of:

CI Usage

In CI environments where interactive prompts aren’t available, use the TURSO_AUTH_TOKEN environment variable as a fallback for authentication:

export TURSO_AUTH_TOKEN="your-token"
lore push