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/webstls.com/httpdocs/uploads/.htaccess
Site	WebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com)
Kind	ssh_agent
Captured at	2026-07-01 22:27:09
Captured SHA	a47be313656860b946ad5573ceb6ce03629f95761c937b463343e55642053d84

Current state on disk

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

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