Cyber/p2ns
1
0
Fork 0
forked from snxraven/p2ns
Code Pull Requests Activity

automatic db migrations on version bump

Browse Source
This commit is contained in:
Raven Scott
2026-05-28 00:19:43 -04:00
parent 2d10e0a4a9
commit 8eb2bc5946
7 changed files with 744 additions and 172 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins/HYPERDB.md
+7 -6
View File
@@ -632,13 +632,14 @@ See [test-scripts/README.md](../test-scripts/README.md) for more information abo
5. **Check status**: Use `sdk.db.replication.getStatus()` to monitor replication health.
6. **Version bumping**: Bump `version` in config.json when making incompatible schema changes (e.g., removing indexes, changing key fields). This creates a new database topic.
6. **Version bumping**: Bump `version` in config.json when making incompatible schema changes (e.g., removing indexes, changing key fields). This creates a new replicated core topic; P2NS migrates local data from the previous version on startup.
7. **Schema migrations**: When bumping version for schema changes:
- Update `version` in `config.json`
- Delete local database: `rm -rf plugin-sites/{domain}/db`
- Restart P2NS
- Coordinate version update with all peers
7. **Schema migrations**: When bumping `version` in `config.json`, P2NS automatically copies all collection data from the previous version's Hypercore into the new one on startup. A manifest at `plugin-sites/{domain}/db/.p2ns-db-version.json` tracks the last migrated version.
- Update `version` in `config.json` (and schema in `hyperdb` if needed)
- Restart P2NS — local data is migrated automatically
- Coordinate the same version bump with all peers so replication uses the same core topic
- If upgrading from before auto-migration and data appears missing, add the old version to `hyperdb.versionHistory` in `config.json` once (e.g. `"versionHistory": ["1.2.1"]`) and restart
## Reference