OptionaldenylistOptionalenableWhether to enable the experimental remote heads gossiping feature
OptionalflushMaximum number of documents Repo.flush (and Repo.shutdown) write to storage concurrently. Defaults to 20.
Tie this to the constraining resource of your StorageAdapterInterface:
OptionalisIndicates whether other peers should persist the sync state of this peer. Sync state is only persisted for non-ephemeral peers
OptionalnetworkA list of network adapters (more can be added at runtime).
OptionalpeerOur unique identifier
OptionalsaveThe debounce rate in milliseconds for saving documents. Defaults to 100ms.
Optional ExperimentalshareWhether to share documents with other peers. By default we announce new documents to everyone and allow everyone access to documents, see the documentation for ShareConfig to override this
Note that this is currently an experimental API and will very likely change without a major release.
OptionalshareNormal peers typically share generously with everyone (meaning we sync all our documents with all peers). A server only syncs documents that a peer explicitly requests by ID.
OptionalshareMaximum number of share-policy resolutions the synchronizer runs
concurrently when re-evaluating which peers each document is shared with.
Defaults to the synchronizer's SHARE_POLICY_CONCURRENCY (10).
Each resolution may invoke an async SharePolicy. On a sync server with many peers and many documents, an unbounded fan-out launches one policy call per peer-document pair at once; this caps how many run together.
OptionalstorageA storage adapter can be provided, or not
OptionalsyncMaximum number of persisted sync-state reads the synchronizer issues concurrently while adding peers to documents (one read per peer-document pair). Defaults to 20.
Like RepoConfig.flushConcurrency, tie this to your StorageAdapterInterface: stay under a filesystem adapter's file-descriptor ceiling, near a browser's per-origin connection cap for an HTTP/1.1-backed adapter, or at or below a database adapter's pool size.
A list of automerge URLs which should never be loaded regardless of what messages are received or what the share policy is. This is useful to avoid loading documents that are known to be too resource intensive.