Your folder

Sync with a folder

Connect a folder of your own and your posts live there as Markdown files. Sync brings the folder and your workspace into line, in both directions.

Sync is still being made. A folder on your computer comes first, and cloud storage after it.

Why connect a folder

Your workspace is a working copy. With a folder connected, the originals of your private and friends-only posts are files you hold, on your own machine or in the cloud storage you already use.

  • You can open and edit them in any Markdown editor, such as Obsidian.
  • Deleting ohm's copy loses nothing: syncing from the folder brings every post back.

Until you connect a folder, ohm holds the only copy of your private and friends-only posts, and the workspace says so.

Connect one

Choose a folder, connect it, and press Sync. The first sync writes every post into it, filed in folders named for your labels. How posts look as files

The folder can be on your computer, or in any cloud storage that keeps a folder in sync.

What Sync does

Sync compares each post in your workspace with its file, and with what was there at the last sync.

In your folderIn your workspaceSync does
A new or changed fileUnchanged since the last syncUpdates your workspace
Unchanged since the last syncA new or changed postWrites it to your folder
ChangedChanged differentlyOverwrites neither. See below
A file removedThe post is still thereAsks you before removing the post

When both sides changed

If you edited a post in your folder and in your workspace since the last sync, neither version is overwritten. Sync puts ohm's version beside your file under a name that says so, reports it, and you choose which one stands.

Sync never publishes

An edit you make to a public post's file arrives in your workspace as a change that is not published yet. Readers see it after you publish.

Writing visibility: public in a file only marks the post. It becomes public when you press Publish.

What you do in the folder, and what Sync makes of it

In your folderSync reads it as
A new fileA new post. Its slug is the file name, and it is private unless the file says otherwise
A file moved to another folderThe post refiled under another label. For a published post this changes its address, which Publish shows first
A file renamedThe same post with a new slug. For a published post, the old address sends readers on
A file deletedA post to ask you about
[[another note]] and ![[image.png]]A link to that post, and a picture. They are kept in the file as you wrote them
Properties edited in Obsidian's own panelThe post's properties

What Sync leaves alone

  • Files that are not posts. Your editor's own settings and anything else in the folder stay yours and are not sent.
  • How you formatted a file. Sync compares posts, not characters. A file you laid out differently is the same post, and it is rewritten only when the post itself changed in your workspace.
  • A file that cannot be read as a post. It is reported to you by name, and nothing is sent.

If a sync is interrupted

Run it again. A sync can be repeated safely, and it picks up where things stand.