centralize

gnosys centralize

Copy this machine's local brain (~/.gnosys/gnosys.db) to seed a central server — a Docker volume or another host.

Usage

gnosys centralize --to /path/to/central-gnosys
gnosys centralize --to /path/to/central-gnosys --force

Options

Option	Description
--to <dir>	Required target directory that receives gnosys.db
--from-local	Source is this machine's local brain (default; local is the only current source)
--force	Overwrite an existing gnosys.db at the target

Behavior

1. Calls centralizeDb({ to: opts.to, force: opts.force }).
2. Uses SQLite's online backup API for a consistent copy (WAL-safe while the source is in use).
3. Creates the target directory if needed.
4. Prints source path, target path, size in MB, and GNOSYS_HOME / container volume guidance on success.

Success output

✓ Seeded central brain:
  from: /Users/you/.gnosys/gnosys.db
  to:   /path/to/central-gnosys/gnosys.db (12.3 MB)

Run the server against it with GNOSYS_HOME=/path/to/central-gnosys, or mount this dir as the container's /data volume.

Errors

No local brain:

centralize failed: No local brain found at /Users/you/.gnosys/gnosys.db

Target exists without --force:

centralize failed: Target already exists: /path/to/central-gnosys/gnosys.db (use --force to overwrite)

Platform notes

macOS

• Source brain: ~/.gnosys/gnosys.db (or $GNOSYS_HOME/gnosys.db).
• Target: any dir (Docker volume mount, NAS path, or another host's .gnosys).
• Use with gnosys serve --transport http on the central host (e.g. Studio) and gnosys connect from clients.

Linux

• Same paths as macOS (usually ~/.gnosys or XDG-aware).
• Systemd timers for remote sync can use the centralized brain.

Windows

• Source: %APPDATA%\gnosys\gnosys.db or %LOCALAPPDATA%\gnosys\gnosys.db (see getMachineConfigPath / paths.ts).
• Target: any writable dir for volume or network share (avoid SMB for the live DB; use for seed only).
• WSL interop: paths may differ; prefer the Windows gnosys for the central if mixing.