Track snapshot base lineage in Django
This commit is contained in:
@@ -138,6 +138,8 @@ SQLite remains the default because it is enough for a single backup server and k
|
||||
## Current Architecture
|
||||
|
||||
The public command surface is Django-first. The old YAML/cron CLI has been retired from the `pobsync` entrypoint.
|
||||
Discovered snapshots are stored in `SnapshotRecord`, including the base snapshot metadata and a nullable SQL link to the
|
||||
base record when it is known.
|
||||
|
||||
The remaining internal engine code still contains reusable backup primitives:
|
||||
|
||||
@@ -148,7 +150,6 @@ The remaining internal engine code still contains reusable backup primitives:
|
||||
|
||||
Next refactor targets:
|
||||
|
||||
- Record discovered snapshots into `SnapshotRecord`.
|
||||
- Surface `SnapshotRecord` data through API/admin views instead of filesystem inspection.
|
||||
- Move more snapshot lifecycle details into typed domain objects.
|
||||
- Replace remaining dictionary-shaped config at engine boundaries.
|
||||
|
||||
Reference in New Issue
Block a user