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/TEMPLATES/repricer_password_change.html
Site	RePricer (repricer.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 21:47:25
Captured SHA	e2315582141b27886d7a52a0e203670a6985485761ded0f4c5912716401939fc

Current state on disk

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

File present	yes
Size	2766 bytes
Current SHA	e2315582141b
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.