TidGi-Desktop/docs/features/WorkspaceConfigSync.md
lin onetwo 57c91866ac Implement workspace config sync via tidgi.config.json
Adds support for syncing workspace configuration to tidgi.config.json in the wiki folder, enabling settings persistence and migration across devices. Introduces new documentation, feature tests, and supporting utilities for config file reading, writing, migration, and validation. Updates step definitions and test helpers to support config sync scenarios, and refactors database config utilities for modularity.
2026-01-09 01:37:06 +08:00

5 KiB

Workspace Configuration Sync

Overview

This document describes how workspace configurations are stored and synced across devices. Some configurations are device-specific and stored locally, while others can be synced via Git through a tidgi.config.json file in the wiki folder.

Configuration Categories

Local-only Fields (stored in database)

These fields are device-specific and should NOT be synced:

Field Reason
id Unique identifier, different per installation
order User preference for sidebar order, device-specific
active Current active state, runtime only
hibernated Current hibernation state, runtime only
lastUrl Last visited URL, device-specific
lastNodeJSArgv Node.js arguments, may vary by device
homeUrl Generated from workspace id
authToken Security token, should not be synced
picturePath Local file path to workspace icon
wikiFolderLocation Absolute path, different per device
mainWikiToLink Absolute path to main wiki
mainWikiID References local workspace id
isSubWiki Structural relationship, set during creation

Syncable Fields (stored in tidgi.config.json)

These fields represent user preferences that should follow the wiki across devices:

Field Description
name Display name for the workspace
port Server port number
gitUrl Git repository URL for syncing
storageService Storage service type (github, gitlab, local)
userName Git username for this workspace
readOnlyMode Whether wiki is in readonly mode
tokenAuth Whether token authentication is enabled
enableHTTPAPI Whether HTTP API is enabled
enableFileSystemWatch Whether file system watching is enabled
ignoreSymlinks Whether to ignore symlinks in file watching
backupOnInterval Whether to backup on interval
syncOnInterval Whether to sync on interval
syncOnStartup Whether to sync on startup
disableAudio Whether audio is disabled
disableNotifications Whether notifications are disabled
hibernateWhenUnused Whether to hibernate when unused
transparentBackground Whether background is transparent
excludedPlugins List of plugins to exclude on startup
tagNames Tag names for sub-wiki routing
includeTagTree Whether to include tag tree for routing
fileSystemPathFilterEnable Whether path filter is enabled
fileSystemPathFilter Path filter expressions
rootTiddler Root tiddler for lazy loading
https HTTPS configuration

File Location

The syncable configuration is stored in:

{wikiFolderLocation}/tidgi.config.json

For main wikis, this is in the wiki root directory (alongside tiddlywiki.info). For sub-wikis, this is in the sub-wiki folder (alongside tiddler files).

File Exclusion

tidgi.config.json is excluded from being treated as a tiddler through multiple mechanisms:

  1. Main wiki: The file is in wiki root, not in tiddlers/ folder, so TiddlyWiki's boot process ignores it
  2. Sub-wiki loading: loadWikiTiddlersWithSubWikis.ts explicitly skips files named tidgi.config.json
  3. File watcher: FileSystemWatcher.ts has tidgi.config.json in excludedFileNames list

File Format

{
  "$schema": "https://tidgi.app/schemas/tidgi.config.schema.json",
  "version": 1,
  "name": "My Wiki",
  "port": 5212,
  "storageService": "github",
  "gitUrl": "https://github.com/user/wiki.git",
  "readOnlyMode": false,
  "enableHTTPAPI": false
}

Only non-default values are saved to keep the file minimal. When loading, missing fields use defaults from syncableConfigDefaultValues.

Loading Priority

When loading a workspace:

  1. Read local config from database (includes device-specific fields)
  2. Read tidgi.config.json from wiki folder (if exists)
  3. Merge syncable config over local config
  4. Apply default values for any missing fields

This ensures synced preferences take precedence over stale local values.

Saving Behavior

When saving workspace config:

  1. Separate fields into local and syncable categories
  2. Save local fields to database (only non-default values)
  3. Save syncable fields to tidgi.config.json (only non-default values)

Migration

For existing workspaces without tidgi.config.json:

  1. On first load, create tidgi.config.json with current syncable values
  2. This happens automatically when workspace is loaded or saved
  3. Existing local database config is preserved