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/abforge.3dshawn.com/billing_payment.cgi
Site	ABForge (abforge.3dshawn.com) on local
Kind	local
Captured at	2026-07-01 16:01:18
Captured SHA	d7a4319a39285a991de90f03f4e3fa247d1d7d53e10bc643f294aa283d1e0bbc

Current state on disk

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

File present	yes
Size	11240 bytes
Current SHA	d7a4319a3928
Same as captured?	yes -- no-op

See exactly what's different →

Preflight compile-check ?

perl compile FAILED — restore is blocked unless you tick "force override" below.

Can't locate MODS/Login.pm in @INC (@INC contains: /var/www/vhosts/abforge.com/httpdocs /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at  line 32.
BEGIN failed--compilation aborted at  line 32.

Confirm restore

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