Restore
Restore
Restore file to captured state
Every captured change carries its SHA-256-addressed content in BLOB_STORE. Restoring writes that content back to the original path — current file gets backed up to <path>.drift_restore_backup_<epoch> before overwrite.
What will change
Preview -- nothing has been written yet.
| Target file | /var/www/vhosts/3dshawn.com/site1/_schema/drift_sense_v2_schema.sql |
| Site | DriftSense self-monitor on local |
| Kind | local |
| Captured at | 2026-07-10 18:57:33 |
| Captured SHA | 3ffaff2dd9732c424ca397241900539c7176d488da2682261c85eadc440f4db8 |
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
| File present | no (new file) |
| Size | unknown |
| Current SHA | |
| Same as captured? | no -- restore will change it |
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.