Sync and export
evolver sync covers both Hub asset synchronization and .gepx archive operations. Inspect the plan first, then use --write explicitly so “show what would happen” is not confused with “materialized locally.”
Sync from the Hub
The supported scopes are purchased, published, and all:
evolver sync --scope purchased
evolver sync --scope published
evolver sync --scope all
Review source, counts, conflicts, and destination paths. Then write explicitly:
evolver sync --scope all --write
Synchronization should retrieve only assets the current node or account is authorized to obtain. SearchFirst and Recipe search do not replace this operation.
Export .gepx
evolver sync --export backup.gepx
Use the archive to back up or migrate GEP history. Record the tool version, source, scope, and checksum information, and keep the migration copy separate from the long-term backup.
Import .gepx
Inspect the import plan first:
evolver sync --import backup.gepx
After checking schemas, asset counts, conflicts, and destination paths, write explicitly:
evolver sync --import backup.gepx --write
Safety boundaries
- Hub synchronization and local archive import have different sources and must be recorded separately.
- Do not overwrite the only backup; keep the original archive until import validation completes.
.gepxmust not containnode_secret, tokens, or signing keys.- Stop on ID conflicts, unknown schemas, or checksum failures instead of inventing a merge rule.
Acceptance
After writing, verify asset counts, IDs, Gene-to-Capsule relationships, and recall behavior. A zero exit code with incomplete content is not a completed migration.
Related pages
EvoX Docs · Developers · Build with GEP