Install, Upgrade, and Migration

This page shows practical command sequences for the most common “lifecycle” operations.

See also:

• docs/docs_file/quick_install.md
• docs/docs_file/upgrade.md
• docs/docs_file/migration_tool.md
• docs/docs_file/manual_migration.md

Example 1 — Install with the wizard (TUI)

cd /opt/proxsave
/opt/proxsave/build/proxsave --install

Example 2 — Install with the wizard (CLI prompts)

Use when SSH/TUI rendering is problematic:

cd /opt/proxsave
/opt/proxsave/build/proxsave --install --cli

Example 3 — Clean reinstall (--new-install)

Use when you want a fresh install flow. This resets most of /opt/proxsave but preserves identity and the build directory.

cd /opt/proxsave
/opt/proxsave/build/proxsave --new-install

CLI prompts:

cd /opt/proxsave
/opt/proxsave/build/proxsave --new-install --cli

Example 4 — Upgrade only the binary (no config changes)

proxsave --upgrade

Example 5 — Upgrade backup.env to add new keys

After upgrading the binary, you can add missing configuration keys (preserving existing values):

proxsave --upgrade-config

Preview only:

proxsave --upgrade-config-dry-run

Example 6 — Migrate from legacy Bash env (–env-migration)

Dry-run first:

proxsave --env-migration-dry-run --old-env /opt/proxsave/env/backup.env

Then migrate for real:

proxsave --env-migration --old-env /opt/proxsave/env/backup.env