Migration¶
Move an existing Pynchy installation to a new checkout or host without copying runtime state that can disrupt the new service.
Copy persistent configuration¶
Stop the old service. Clone the private personalization repository into the new checkout first:
git clone [email protected]:YOUR-ACCOUNT/pynchy-personalization.git \
data/personalization
Then copy runtime data without replacing that nested repository, and copy the root .env when it contains gateway, channel, or provider secrets:
rsync -a --exclude personalization OLD_PYNCHY/data/ NEW_PYNCHY/data/
cp OLD_PYNCHY/.env NEW_PYNCHY/.env
For an installation that still uses root config.toml and litellm_config.yaml, initialize a private personalization repository, move their contents to pynchy.toml and litellm.yaml, and remove gateway.litellm_config from the TOML. Pynchy no longer reads the root files. Move durable [jobs.<name>] declarations into automations/<name>.toml documents when convenient; the validator still accepts non-colliding [jobs] declarations during migration.
Validate before the first start:
Do not copy data/deploy_continuation.json; it can trigger a rollback to an old commit on the new host.
If data/neonize.db moves successfully, skip WhatsApp QR authentication unless the linked-device session expired. Do not blindly copy LiteLLM's PostgreSQL data between Linux Docker and macOS Apple Container deployments; let the gateway recreate its database unless you need its internal history.
Review runtime-only state¶
data/ can contain host-specific worktrees, repositories, and message history. If startup stalls on git fetch or a repo-backed workspace because the new host cannot reach GitHub yet, move data/worktrees/ and data/repos/ aside or temporarily remove the affected repo profile entries. Prioritize one healthy service over preserving every historical row.
Pynchy prunes migration safety copies from data/migration-backups/ after a successful deploy restart, retaining the newest three directories. Inspect or run cleanup explicitly with:
The command considers only direct child directories and ignores files and symlinks.