Restore
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/assets/js/fingerprint.js |
| Site | WebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com) |
| Kind | ssh_agent |
| Captured at | 2026-07-02 17:01:29 |
| Captured SHA | 578cec2be731e28d8f9e488c3b7ee6d875e3f10c38c43d0f924a222d117f7bc1 |
Current state on disk
Live check just now. If SHAs match, the restore is a no-op.
| File present | yes |
| Size | 5525 bytes |
| Current SHA | 578cec2be731 |
| Same as captured? | yes -- no-op |
Confirm restore
Backs current content to <target>.drift_restore_backup_<epoch>, writes the captured content, verifies SHA post-write.