| 1 |
# synckit |
| 2 |
|
| 3 |
End-to-end-encrypted sync: the client SDK and the local config store. |
| 4 |
|
| 5 |
Extracted from the MNW monorepo (2026-07-24) so synckit can version and deploy |
| 6 |
independently. Two standalone crates, no root workspace (each builds on its own, |
| 7 |
matching the ecosystem convention): |
| 8 |
|
| 9 |
- **`synckit-client`** — the sync SDK: transport, crypto, the declarative |
| 10 |
`SyncStore` engine over SQLite. Internal; consumed by path or git dependency, |
| 11 |
never published to crates.io. |
| 12 |
- **`synckit-config`** — a local key/value settings store with per-key sync |
| 13 |
postures. The store half of portable config; usable with no network, so a |
| 14 |
no-sync consumer (a TUI remembering a theme) links it without the SDK. The |
| 15 |
sync adapter that turns a `ConfigSpec` into a `SyncTable` lives in |
| 16 |
`synckit-client` behind its `store` feature. |
| 17 |
|
| 18 |
The synckit **server** still lives in the MNW server. Splitting it into a |
| 19 |
standalone service on its own VPS is a separate, later effort — see the wiki |
| 20 |
note `mnw-strategy-synckit-vps-separation`, triggered by the first external |
| 21 |
developer. |
| 22 |
|