6. Sync configuration
6.1 Configuration model
A sync configuration (roughly one per signed-in user) includes:
- Coordinator server URL and authenticated user
- Sync interval in minutes (example default: 5)
- A list of entries, each linking a source folder to sync behavior
Typical fields per entry:
| Field | Meaning |
|---|---|
| Source folder | Local path to watch / ingest |
| Target book | Destination book |
| Section | Optional section binding |
| Include subfolders | Recurse into child directories |
| Allow delete sync | Whether local deletes propagate to the server (may delete server-side content—high risk; configure carefully) |
| Enabled | Temporarily disable an entry |
| Overflow books | Additional books when splitting load |
| Priority | Hint when multiple entries compete |
Source folders and books
- Each entry usually maps one source folder to one or more books (primary + overflow).
- After sign-in, the UI lists books you may use.
Relative paths
If you enter a relative path, the tool tries to resolve it from the process working directory and common user folders (Desktop, Documents, Downloads). In production, specify absolute paths.
Note: In the beta release, relative paths are not supported. Use absolute paths only.
Duplicate or nested folders
You cannot register the same folder on multiple entries, nor a folder that is a parent/child of another entry’s folder; save will fail with an explanatory error. This prevents double-uploading the same files.
Interval and caveats
- Interval is in minutes; very short intervals increase load on the network and server.
- First sync or large batches may take time—check logs.
- Sleep or offline periods delay or fail runs until connectivity returns.
After changes, run manual sync once to validate behavior.