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/MODS/ContactForge/Subscriptions.pm
SiteContactForge (crm.3dshawn.com) on local
Kindlocal
Captured at2026-07-01 15:02:56
Captured SHA4666582fbce19d9d83c76fe33055db6c39c7304b71ec239f761856d9fc5ad7fa
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
File presentyes
Size23568 bytes
Current SHA4666582fbce1
Same as captured?yes -- no-op
Preflight compile-check ?
perl compiles cleanly — restore is safe to proceed.
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.
Cancel Logged to RESTORE_LOG regardless of outcome.