Cloud Sync Details

Cloud Sync encrypts and synchronizes your Swixter profiles across machines via a secure API.

How It Works

Profiles are encrypted locally before upload
Encrypted data is sent to the Swixter sync API
Other machines pull and decrypt changes
Conflict resolution determines which version wins when profiles change on multiple machines

{
  "sync": {
    "autoSync": true,
    "interval": 300,
    "conflictStrategy": "lastWriteWins",
    "endpoint": "https://sync.swixter.cc"
  }
}

Option	Description	Default
`autoSync`	Automatically sync on profile changes	`true`
`interval`	Background sync interval in seconds	`300`
`conflictStrategy`	How to resolve conflicts	`"lastWriteWins"`
`endpoint`	Sync API endpoint	`"https://sync.swixter.cc"`

Profiles are encrypted using AES-256-GCM before transmission:

API keys in profiles are encrypted at rest on the server. The server never sees plaintext API keys.

When the same profile is modified on two machines before syncing:

Strategy	Behavior
`lastWriteWins`	Most recent modification takes precedence
`manual`	Prompt user to choose which version to keep

When manual strategy is active, conflicting profiles appear in:

swixter sync status
# Shows: 2 profiles with conflicts

Review and resolve:

swixter sync resolve <profile-name>
# Shows diff between versions
# Choose: local / remote / merge

The following data is synced:

Not synced:

# Check status
swixter sync status

# Force re-authentication
swixter sync logout
swixter sync login

# Force a pull
swixter sync pull

# Check for conflicts
swixter sync status

swixter sync logout
# This removes auth tokens. Local profiles are preserved.
swixter sync login
# Re-authenticate and re-sync.

For teams or users who want to run their own sync server, the sync endpoint can be customized:

{
  "sync": {
    "endpoint": "https://sync.my-company.com"
  }
}

The sync API is a Workers-compatible REST API. See the Swixter GitHub repository for API documentation.