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/crm.3dshawn.com/TEMPLATES/cf_marketing.html |
| Site | ContactForge (crm.3dshawn.com) on local |
| Kind | local |
| Captured at | 2026-07-11 08:17:32 |
| Captured SHA | 54b8b2837cf72365985e8bf85c8d8af7be3101b82c01cd31a78087d1a5c6f4dd |
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
| File present | yes |
| Size | 5728 bytes |
| Current SHA | 54b8b2837cf7 |
| Same as captured? | yes -- no-op |
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.