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/repricer.3dshawn.com/admin_emails.cgi
Site	RePricer (repricer.3dshawn.com) on local
Kind	local
Captured at	2026-07-11 18:33:27
Captured SHA	316a3a7ef4b37d24df01665ba6a3de42beb6dceacd08d8b84007cd451bcc2b60

Current state on disk

Live check just now. If SHAs match, the restore is a no-op.

File present	yes
Size	61578 bytes
Current SHA	316a3a7ef4b3
Same as captured?	yes -- no-op

See exactly what's different →

Confirm restore

Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.