Merge data with your central Repoch data via your Repoch Server. This one-way, additive merge safely transfers sessions, datasets and models without modifying existing records.
Always back up your target database before merging. While the operation is designed to be safe and never modifies existing data, backups provide an additional safety net.
Prerequisites
Central Repoch server running and network-accessible
Schemas synced (run alembic upgrade head if versions differ)
Server configured via repoch client, or use --server-host/--server-port flags
Step 1: Check Status repoch merge status --db-path repoch_data/database.db
Automatically checks against the currently connected server. repoch merge status --db-path repoch_data/database.db \ --server-host 192.168.1.100 \ --server-port 8000
Alternatively, choose a specific server. The output shows a table with three columns:
New : Records that will be insertedConflict : Same ID, different data (will be skipped)Identical : Already on server (will be skipped)
Step 2: Push Data Execute the merge and upload session files:
repoch merge push --db-path repoch_data/database.db \ --data-dir repoch_data/data_storage
A confirmation prompt appears before execution. The merge is additive-only :
Existing server data is never modified
Conflicting records are skipped and logged
Session files (videos, audio, timeseries) are automatically uploaded
Dry Run
Skip Confirmation
Explicit Server
Preview without executing: repoch merge push --db-path repoch_data/database.db \ --data-dir repoch_data/data_storage \ --dry-run
repoch merge push --db-path repoch_data/database.db \ --data-dir repoch_data/data_storage \ --yes
repoch merge push --db-path repoch_data/database.db \ --data-dir repoch_data/data_storage \ --server-host 192.168.1.100 \ --server-port 8000
Next Steps
Redis Setup Set up Redis for background workers and distributed processing
