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/Login.pm
Site	ContactForge (crm.3dshawn.com) on local
Kind	local
Captured at	2026-07-02 15:46:15
Captured SHA	66598a4944654af433c8661325e53ca3a102b3a424f0e56e0f1b528fe20a0a69

Current state on disk

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

File present	yes
Size	24428 bytes
Current SHA	66598a494465
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/ContactForge/Config.pm in @INC (@INC contains: /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 29.
BEGIN failed--compilation aborted at  line 29.

Confirm restore

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