Cairn

Cairn 0.1.18

The same files are in GitHub's release v0.1.18.

Updates now come from cairn.storage, where every release's files are, and from GitHub only when that does not answer; the web interface adds and renames folders, switches between a light and a dark theme, and opens an item from anywhere in its name's cell.

This is early software. Keep another copy of anything you put through it.

Linux (x86_64, static):

sha256sum -c cairn-0.1.18-x86_64-unknown-linux-musl.tar.gz.sha256
tar xzf cairn-0.1.18-x86_64-unknown-linux-musl.tar.gz

macOS: unpack both .app.tar.gz into ~/Applications; README.md has the launchd agent for Cairn Sync.app. Windows: put cairn-0.1.18-windows-x86_64.exe and cairn-tray-0.1.18-windows-x86_64.exe in a folder of their own as cairn.exe and cairn-tray.exe. cairn-0.1.18-linux-x86_64 is the bare Linux program, which installed copies update to. update.json is the signed list of this release's files that every installed copy checks.

Every file is at https://cairn.storage/download/0.1.18.html and in GitHub's release v0.1.18, each with its SHA-256.

The server has changed in this release: upgrade it before the clients.

Changes in 0.1.18

Added:

  • Folders added and renamed in the web interface. The + beside Folders in the sidebar adds a folder of the user's own, which they manage and nobody else reaches until given access: what they call it, and its name on the server, made of that (Family photos as family-photos) until they change it. Each folder has a page of its settings, opened from Folder settings under it in the sidebar or from its level beside its name, which until now did nothing when clicked: its name on the server, which a manager renames there, the user's own name for it, their access, and the command that syncs it on a computer.
  • A folder renamed while the server serves, by a manager of it, in one transaction, its chunks left where they are: what was begun by the former name as it was renamed goes on in the same folder, a commit or a web upload in flight lands in it, and the former name goes on reaching it as after cairn-server folder rename, which stays for the server stopped. The API is POST /v1/folders and POST /v1/ns/{ns}/rename (docs/protocol.md); a name that is or was another folder's is refused, saying nothing of that folder.
  • A light and a dark theme in the web interface, switched by a button at the right end of the top bar (on the sign-in page and a public link's page too) and chosen in Settings, Theme, which also goes back to following the device. Kept in that browser; until something is chosen it is light or dark as the device is, as before.

Changed:

  • Updates come from cairn.storage, where each release's files are, with its downloads page (https://cairn.storage/download/), and from GitHub's latest release only when that does not answer. cairn update says which feed answered, and what the one before it said when it did not, so a fallback never hides a feed that is down. Several feeds, comma-separated, are asked in order wherever one is named: a build's CAIRN_UPDATE_FEED, update-settings.json's feed, --feed. A release's update.json names its files beside it, so the one signed file serves from either; copies of 0.1.17 and before, which ask GitHub alone, take this release there.
  • In the web's file list and on Shared with me, a click anywhere in the name's cell opens the item: its icon and the space around and beside the name too, where only the name itself did.