📄️ Sync Server
lo-fi doesn't sync by default. It's offline-first, sync-optional. I built it that way because my goal is to support nice local-only anonymous experiences, and add sync & realtime on as an incentive to sign up (and potentially subscribe) to your app.
📄️ Authenticating Sync
To connect to sync, you must create an auth endpoint. This can be done automatically on the same server you use for sync, or you can define a custom endpoint on a different server.
📄️ Connecting a Client
To connect your client to the server, you must pass it sync configuration.
📄️ Presence & Profiles
Once you're syncing, presence info is available on client.sync.presence (where client is your instance of Client).
📄️ Synchronizing files
When you create files locally, they are flagged as unsynced until you next go online.
📄️ Advanced: Transports
lo-fi can sync over HTTP requests or WebSockets. By default, it automatically uses HTTP when a user is the only one connected to a library, and switches to WebSockets when other users are online.