b73ca73776
- Setting dialogue very slightly refined. - The hodgepodge inside the `Hatch` pane has been sorted into more explicit categorised panes. - Applying the settings will now be more informative. New features: - Word-segmented chunk building on users language. Fixed: - Sending chunks on `Send chunk in bulk` are now buffered to avoid the out-of-memory error. - `Send chunk in bulk` is back to default disabled. - Merging conflicts of JSON files are now works fine even if it contains `null`. Development: - Implemented the logic for automatically generating the stub of document for the setting dialogue.
20 KiB
NOTE: This document not completed. I'll improve this doc in a while. but your contributions are always welcome.
Settings of Self-hosted LiveSync
There are many settings in Self-hosted LiveSync. This document describes each setting in detail (not how-to). Configuration and settings are divided into several categories and indicated by icons. The icon is as follows:
0. Update Information
This pane shows version up information. You can check what has been changed in recent versions.
1. Setup
This pane is used for setting up Self-hosted LiveSync. There are several options to set up Self-hosted LiveSync.
1. Quick Setup
Most preferred method to setup Self-hosted LiveSync. You can setup Self-hosted LiveSync with a few clicks.
Use the copied setup URI
Setup the Self-hosted LiveSync with the setup URI which is copied from another device or the setup script.
Minimal setup
Step-by-step setup for Self-hosted LiveSync. You can setup Self-hosted LiveSync manually with Minimal setting items.
Enable LiveSync on this device as the setup was completed manually
This button only appears when the setup was not completed. If you have completed the setup manually, you can enable LiveSync on this device by this button.
2. To setup the other devices
Copy current settings as a new setup URI
You can copy the current settings as a new setup URI. And this URI can be used to setup the other devices as Use the copied setup URI.
3. Reset
Discard existing settings and databases
Reset the Self-hosted LiveSync settings and databases. Hazardous operation. Please be careful when using this.
4. Enable extra and advanced features
To keep the set-up dialogue simple, some panes are hidden in default. You can enable them here.
Enable advanced features
Setting key: useAdvancedMode
Following panes will be shown when you enable this setting.
| Icon | Description |
|---|---|
| 🚦 | 5. Selector (Advanced) |
| 🔌 | 6. Customization sync (Advanced) |
| 🔧 | 8. Advanced (Advanced) |
Enable power user features
Setting key: usePowerUserMode
Following panes will be shown when you enable this setting.
| Icon | Description |
|---|---|
| 💪 | 9. Power users (Power User) |
Enable edge case treatment features
Setting key: useEdgeCaseMode
Following panes will be shown when you enable this setting.
| Icon | Description |
|---|---|
| 🩹 | 10. Patches (Edge Case) |
2. General Settings
1. Appearance
Display Language
Setting key: displayLanguage
You can change the display language. It is independent of the system language and/or Obsidian's language. Note: Not all messages have been translated. And, please revert to "Default" when reporting errors. Of course, your contribution to translation is always welcome!
Show status inside the editor
Setting key: showStatusOnEditor
We can show the status of synchronisation inside the editor.
Reflected after reboot
Show status as icons only
Setting key: showOnlyIconsOnEditor
Show status as icons only. This is useful when you want to save space on the status bar.
Show status on the status bar
Setting key: showStatusOnStatusbar
We can show the status of synchronisation on the status bar. (Default: On)
2. Logging
Show only notifications
Setting key: lessInformationInLog
Prevent logging and show only notification. Please disable when you report the logs
Verbose Log
Setting key: showVerboseLog
Show verbose log. Please enable when you report the logs
3. Remote Configuration
1. Remote Server
Remote Type
Setting key: remoteType
Remote server type
2. Notification
Notify when the estimated remote storage size exceeds on start up
Setting key: notifyThresholdOfRemoteStorageSize
MB (0 to disable). We can get a notification when the estimated remote storage size exceeds this value.
3. Confidentiality
End-to-End Encryption
Setting key: encrypt
Enable end-to-end encryption. enabling this is recommend. If you change the passphrase, you need to rebuild databases (You will be informed).
Passphrase
Setting key: passphrase
Encrypting passphrase. If you change the passphrase, you need to rebuild databases (You will be informed).
Path Obfuscation
Setting key: usePathObfuscation
In default, the path of the file is not obfuscated to improve the performance. If you enable this, the path of the file will be obfuscated. This is useful when you want to hide the path of the file.
Use dynamic iteration count (Experimental)
Setting key: useDynamicIterationCount
This is an experimental feature and not recommended. If you enable this, the iteration count of the encryption will be dynamically determined. This is useful when you want to improve the performance.
now writing from here onwards, sorry
4. Minio,S3,R2
Endpoint URL
Setting key: endpoint
Access Key
Setting key: accessKey
Secret Key
Setting key: secretKey
Region
Setting key: region
Bucket Name
Setting key: bucket
Use Custom HTTP Handler
Setting key: useCustomRequestHandler If your Object Storage could not configured accepting CORS, enable this.
Test Connection
Apply Settings
5. CouchDB
URI
Setting key: couchDB_URI
Username
Setting key: couchDB_USER username
Password
Setting key: couchDB_PASSWORD password
Database name
Setting key: couchDB_DBNAME
Test Database Connection
Open database connection. If the remote database is not found and you have the privilege to create a database, the database will be created.
Check and fix database configuration
Check the database configuration, and fix if there are any problems.
Apply Settings
4. Sync Settings
1. Synchronization Preset
Presets
Setting key: preset Apply preset configuration
2. Synchronization Methods
Sync Mode
Setting key: syncMode
Periodic Sync interval
Setting key: periodicReplicationInterval Interval (sec)
Sync on Save
Setting key: syncOnSave When you save a file, sync automatically
Sync on Editor Save
Setting key: syncOnEditorSave When you save a file in the editor, sync automatically
Sync on File Open
Setting key: syncOnFileOpen When you open a file, sync automatically
Sync on Start
Setting key: syncOnStart Start synchronization after launching Obsidian.
Sync after merging file
Setting key: syncAfterMerge Sync automatically after merging files
3. Update thinning
Batch database update
Setting key: batchSave Reducing the frequency with which on-disk changes are reflected into the DB
Minimum delay for batch database updating
Setting key: batchSaveMinimumDelay Seconds. Saving to the local database will be delayed until this value after we stop typing or saving.
Maximum delay for batch database updating
Setting key: batchSaveMaximumDelay Saving will be performed forcefully after this number of seconds.
4. Deletion Propagation (Advanced)
Use the trash bin
Setting key: trashInsteadDelete Do not delete files that are deleted in remote, just move to trash.
Keep empty folder
Setting key: doNotDeleteFolder Normally, a folder is deleted when it becomes empty after a synchronization. Enabling this will prevent it from getting deleted
5. Conflict resolution (Advanced)
Always overwrite with a newer file (beta)
Setting key: resolveConflictsByNewerFile (Def off) Resolve conflicts by newer files automatically.
Postpone resolution of inactive files
Setting key: checkConflictOnlyOnOpen
Postpone manual resolution of inactive files
Setting key: showMergeDialogOnlyOnActive
6. Sync settings via markdown (Advanced)
Filename
Setting key: settingSyncFile If you set this, all settings are saved in a markdown file. You will be notified when new settings arrive. You can set different files by the platform.
Write credentials in the file
Setting key: writeCredentialsForSettingSync (Not recommended) If set, credentials will be stored in the file.
Notify all setting files
Setting key: notifyAllSettingSyncFile
7. Hidden files (Advanced)
Hidden file synchronization
Enable Hidden files sync
Scan for hidden files before replication
Setting key: syncInternalFilesBeforeReplication
Scan hidden files periodically
Setting key: syncInternalFilesInterval Seconds, 0 to disable
5. Selector (Advanced)
1. Normal Files
Synchronising files
(RegExp) Empty to sync all files. Set filter as a regular expression to limit synchronising files.
Non-Synchronising files
(RegExp) If this is set, any changes to local and remote files that match this will be skipped.
Maximum file size
Setting key: syncMaxSizeInMB (MB) If this is set, changes to local and remote files that are larger than this will be skipped. If the file becomes smaller again, a newer one will be used.
(Beta) Use ignore files
Setting key: useIgnoreFiles If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.
Ignore files
Setting key: ignoreFiles
We can use multiple ignore files, e.g.) .gitignore, .dockerignore
2. Hidden Files (Advanced)
Ignore patterns
Add default patterns
6. Customization sync (Advanced)
1. Customization Sync
Device name
Setting key: deviceAndVaultName Unique name between all synchronized devices. To edit this setting, please disable customization sync once.
Per-file-saved customization sync
Setting key: usePluginSyncV2 If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.
Enable customization sync
Setting key: usePluginSync
Scan customization automatically
Setting key: autoSweepPlugins Scan customization before replicating.
Scan customization periodically
Setting key: autoSweepPluginsPeriodic Scan customization every 1 minute.
Notify customized
Setting key: notifyPluginOrSettingUpdated Notify when other device has newly customized.
Open
Open the dialog
7. Hatch
1. Reporting Issue
Make report to inform the issue
Write logs into the file
Setting key: writeLogToTheFile Warning! This will have a serious impact on performance. And the logs will not be synchronised under the default name. Please be careful with logs; they often contain your confidential information.
2. Scram Switches
Suspend file watching
Setting key: suspendFileWatching Stop watching for file change.
Suspend database reflecting
Setting key: suspendParseReplicationResult Stop reflecting database changes to storage files.
3. Recovery and Repair
Recreate missing chunks for all files
This will recreate chunks for all files. If there were missing chunks, this may fix the errors.
Verify and repair all files
Compare the content of files between on local database and storage. If not matched, you will be asked which one you want to keep.
Check and convert non-path-obfuscated files
4. Reset
Back to non-configured
Delete all customization sync data
8. Advanced (Advanced)
1. Memory cache
Memory cache size (by total items)
Setting key: hashCacheMaxCount
Memory cache size (by total characters)
Setting key: hashCacheMaxAmount (Mega chars)
2. Local Database Tweak
Enhance chunk size
Setting key: customChunkSize
Use splitting-limit-capped chunk splitter
Setting key: enableChunkSplitterV2 If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.
Use Segmented-splitter
Setting key: useSegmenter If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.
3. Transfer Tweak
Fetch chunks on demand
Setting key: readChunksOnline (ex. Read chunks online) If this option is enabled, LiveSync reads chunks online directly instead of replicating them locally. Increasing Custom chunk size is recommended.
Batch size of on-demand fetching
Setting key: concurrencyOfReadChunksOnline
The delay for consecutive on-demand fetches
Setting key: minimumIntervalOfReadChunksOnline
Send chunks in bulk
Setting key: sendChunksBulk If this enabled, all chunks will be sent in bulk. This is useful for the environment that has a high latency.
Maximum size of chunks to send in one request
Setting key: sendChunksBulkMaxSize MB
9. Power users (Power User)
1. Remote Database Tweak
Incubate Chunks in Document (Beta)
Setting key: useEden If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.
Maximum Incubating Chunks
Setting key: maxChunksInEden The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.
Maximum Incubating Chunk Size
Setting key: maxTotalLengthInEden The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.
Maximum Incubation Period
Setting key: maxAgeInEden The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.
Data Compression (Experimental)
Setting key: enableCompression
2. CouchDB Connection Tweak
Batch size
Setting key: batch_size Number of change feed items to process at a time. Defaults to 50. Minimum is 2.
Batch limit
Setting key: batches_limit Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.
Use timeouts instead of heartbeats
Setting key: useTimeouts If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.
3. Configuration Encryption
Encrypting sensitive configuration items
Setting key: configPassphraseStore
Passphrase of sensitive configuration items
Setting key: configPassphrase
This passphrase will not be copied to another device. It will be set to Default until you configure it again.
10. Patches (Edge Case)
1. Compatibility (Metadata)
Do not keep metadata of deleted files.
Setting key: deleteMetadataOfDeletedFiles
Delete old metadata of deleted files on start-up
Setting key: automaticallyDeleteMetadataOfDeletedFiles (Days passed, 0 to disable automatic-deletion)
2. Compatibility (Conflict Behaviour)
Always resolve conflicts manually
Setting key: disableMarkdownAutoMerge If this switch is turned on, a merge dialog will be displayed, even if the sensible-merge is possible automatically. (Turn on to previous behavior)
Always reflect synchronized changes even if the note has a conflict
Setting key: writeDocumentsIfConflicted Turn on to previous behavior
3. Compatibility (Database structure)
(Obsolete) Use an old adapter for compatibility (obsolete)
Setting key: useIndexedDBAdapter Before v0.17.16, we used an old adapter for the local database. Now the new adapter is preferred. However, it needs local database rebuilding. Please disable this toggle when you have enough time. If leave it enabled, also while fetching from the remote database, you will be asked to disable this.
Compute revisions for chunks (Previous behaviour)
Setting key: doNotUseFixedRevisionForChunks If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)
Handle files as Case-Sensitive
Setting key: handleFilenameCaseSensitive If this enabled, All files are handled as case-Sensitive (Previous behaviour).
4. Compatibility (Internal API Usage)
Scan changes on customization sync
Setting key: watchInternalFileChanges Do not use internal API
5. Edge case addressing (Database)
Database suffix
Setting key: additionalSuffixOfDatabaseName LiveSync could not handle multiple vaults which have same name without different prefix, This should be automatically configured.
The Hash algorithm for chunk IDs (Experimental)
Setting key: hashAlg
6. Edge case addressing (Behaviour)
Fetch database with previous behaviour
Setting key: doNotSuspendOnFetching
Keep empty folder
Setting key: doNotDeleteFolder Normally, a folder is deleted when it becomes empty after a synchronization. Enabling this will prevent it from getting deleted
7. Edge case addressing (Processing)
Do not split chunks in the background
Setting key: disableWorkerForGeneratingChunks If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).
Process small files in the foreground
Setting key: processSmallFilesInUIThread If enabled, the file under 1kb will be processed in the UI thread.
8. Compatibility (Trouble addressed)
Do not check configuration mismatch before replication
Setting key: disableCheckingConfigMismatch
11. Maintenance
1. Scram!
Lock remote
Lock remote to prevent synchronization with other devices.
Emergency restart
place the flag file to prevent all operation and restart.
2. Data-complementary Operations
Resend
Resend all chunks to the remote.
Reset journal received history
Initialise journal received history. On the next sync, every item except this device sent will be downloaded again.
Reset journal sent history
Initialise journal sent history. On the next sync, every item except this device received will be sent again.
3. Rebuilding Operations (Local)
Fetch from remote
Restore or reconstruct local database from remote.
Fetch rebuilt DB (Save local documents before)
Restore or reconstruct local database from remote database but use local chunks.
4. Total Overhaul
Rebuild everything
Rebuild local and remote database with local files.
5. Rebuilding Operations (Remote Only)
Perform compaction
Compaction discards all of Eden in the non-latest revisions, reducing the storage usage. However, this operation requires the same free space on the remote as the current database.
Overwrite remote
Overwrite remote with local DB and passphrase.
Reset all journal counter
Initialise all journal history, On the next sync, every item will be received and sent.
Purge all journal counter
Purge all sending and downloading cache.
Make empty the bucket
Delete all data on the remote.
6. Niches
(Obsolete) Clean up databases
Delete unused chunks to shrink the database. However, this feature could be not effective in some cases. Please use rebuild everything instead.