Your SQLly setup on every Mac, through iCloud

SQLly now syncs saved connections, snippets, queries and settings between your Macs through your own iCloud Drive. Off by default; passwords stay put.

By

SQLly on the Mac can now keep your saved connections, snippets, SQL Library queries and settings the same on every Mac you use, through your own iCloud Drive. It is off until you turn it on, and your passwords never leave the Mac they were saved on.

It ships in the next macOS release of the direct-download edition. Turn it on in Settings ▸ Workspace ▸ iCloud Sync.

Why now

Someone asked Sequel Ace for native iCloud sync, and they were right to. I have a desktop Mac and a laptop, and for months my answer to "how do I keep SQLly the same on both" was everything is a file, point a sync tool at the folder. That works, but it has an edge: SQLly reads its connection file at launch, so a sync tool that swaps the file underneath a running app gets overwritten by the next save. It was a workaround, not a feature.

What travels

SyncsNever syncs
Saved connections, with their notes, clients, projects, environments, colors, icons and tunnel profilesPasswords, SSH key passphrases, tokens and API keys
Snippets and quick actionsShared logins
SQL Library queries (default folder, up to 1 MB each)Query history and open tabs
Appearance, editor, shortcut, formatting, sensitive-column, explorer, tab and transaction settingsAI and MCP settings, and anything that points at a program or file on one Mac

The secrets column is the one I cared about most. Before anything is written to iCloud, every password slot in a connection or tunnel profile is emptied, whichever slot it is: the SQL login, the proxy, the SSH target and jump host, Redis Sentinel. A connection that arrives on your other Mac asks for its password the first time you connect there, and from then on each Mac keeps its own. When you rename that connection on the laptop, the desktop takes the new name and keeps the password it already had.

How two Macs agree

The lazy way to build this is to drop one big settings file into iCloud Drive and let iCloud sort it out. iCloud sorts it out by keeping one copy and quietly setting the other aside, which is fine for a photo and not fine for the connection you added on the other machine five minutes ago.

So each Mac writes only its own file into a SQLLY Sync folder, and reads everyone else's. Nothing ever has two writers. Then SQLly merges item by item:

  • The newest change to each item wins. Edit one connection on the laptop and a different one on the desktop, and you keep both edits.
  • Deletes stick. A delete is recorded as a tombstone that is never thrown away, so the old Mac in the closet can't bring a connection back from the dead next time it wakes up.
  • Your SQL is never discarded. If a query you edited loses to a newer version from another Mac, your version is saved beside it as a conflicted copy, and that copy syncs too.
  • A Mac that joins later takes the shared settings. Its own connections, snippets and queries are added to the pile.

Failing safely

iCloud Drive is a file system with opinions. Files show up half-downloaded, as placeholders, or not at all. A newer SQLly on one Mac might write a format an older one doesn't understand. None of those should cost you data, so:

  • A damaged, unfinished or newer-version sync file is skipped whole and named in the Settings pane. Nothing on your Mac changes because of it.
  • An item missing from a file never means "deleted". Only a tombstone deletes, so skipping a file can delay a change but never lose one.
  • If one of your own settings files can't be read, SQLly doesn't send it and doesn't treat it as deleted either.
  • If the Mac isn't signed in to iCloud, or iCloud Drive is off, the pane says which, and nothing syncs until you fix it.

Why iCloud Drive and not CloudKit

I'd have liked CloudKit. It needs iCloud entitlements, and the direct-download build doesn't have them, so SQLly uses a plain folder in your iCloud Drive that macOS syncs like any other. You can see it in Finder, which I count as a feature: your setup is in your account, readable by you, and never routed through a server of mine.

The same constraint is why the Mac App Store edition doesn't offer this yet. It runs in Apple's sandbox and can't reach that folder. Help ▸ Mac App Store Edition now lists iCloud sync among its differences, and File ▸ Export Connections and Import Connections still move connections between Macs there. Windows and Linux don't have it either; the file-based approach is still the answer there.

Turning it on, and off

Open Settings ▸ Workspace ▸ iCloud Sync and tick Sync with iCloud on each Mac. SQLly syncs straight away, then about once a minute while it is open, and whenever you press Sync Now. Connections, snippets and queries from your other Macs show up as they arrive; settings take full effect the next time SQLly starts.

Untick it and syncing stops on that Mac. Nothing is removed from the Mac or from iCloud.

I tested the merge rules, the secret stripping and the damaged-file handling with a temporary folder standing in for iCloud and two simulated Macs. Real iCloud across real Macs is the part I'll be watching once it is in your hands, so if something syncs oddly, send feedback from the app and tell me what you saw.

The full reference is in the docs: iCloud Drive sync.