Sync a space with a folder on your Mac

Pair a folder on your own Mac directly with a space on a cloud instance. There is no local space in between: the Memex relay app on the Mac (memex-relay) holds one outbound connection to the instance, and each sync asks the Mac live for the folder's files. Edits go both ways, and a file changed on both sides is kept as a conflict, never overwritten. It works while the Mac is on.

On the Mac, once

  1. Pair the relay with the instance as yourself, if you have not already (the same pairing the cloud inbox uses for iMessage): memex-relay pair https://<instance> <your user id>. The API token is read from the keyboard, never from the command line.
  2. Share the folder: memex-relay folders add ~/Documents/Acme. Only folders you list here can ever be reached, and the list starts empty. memex-relay folders list shows it, memex-relay folders remove <folder> takes one off.
  3. Start the relay (or restart it after a change): memex-relay run. memex-relay status shows the pairing, the connection and the shared folders.

The list lives only on the Mac. The instance can neither read it nor change it.

In the space

On the space's Synchronizations page choose Folder on my Mac. The picker asks your Mac which folders it shares and lets you open their sub-folders; a folder named like the space is suggested first. The preview reads both sides through the relay and writes nothing. Start syncing creates the sync, which then runs every 15 minutes, or when you press Sync now.

If the Mac does not answer, the picker says so and offers Try again instead of a folder list.

What can and cannot be reached

How it behaves

Not the same as "Folder on this computer"

Folder on this computer is for a mesh that itself runs on your Mac (LocalMesh). Folder on my Mac is for a space on a cloud instance; the folder stays on your Mac and the relay is the only path to it.

See the Guide for directions, the first sync and conflicts, and the design for how the relay request is checked on both ends.