Broadcast
Cross-portfolio

Broadcast a captured file to other sites

Take one file that DriftSense already captured on one site and write those exact bytes to the same path on any set of your other monitored sites. Turns "there's drift" into "there's a fix" in one click.

i
New here? What Broadcast does + when to use it

Every file DriftSense has ever captured lives in BLOB_STORE keyed by SHA-256. Broadcast lets you grab one of those captured versions and write those exact bytes to the same file path on other sites you monitor. It's the fastest way to sync a fix across your whole portfolio when the same file lives on multiple sites and one of them has the "canonical" version.

Common use cases
  • Divergence spotted on Portfolio drift — push the good copy to the drifted sites
  • Fixed a bug on Site A, need the same fix on Sites B/C/D that share the file
  • Rolled out a new .htaccess, config, or template across the portfolio
  • Onboarding a new site: copy shared config from an established sibling
How it works — 3 steps
  1. Pick a source — any captured file. Click "Use as source" in the list below, or jump from any file changes row.
  2. Pick targets — tick the monitored sites you want to receive the file. Target path defaults to same basename inside each site's scan_path, override per row if needed.
  3. Confirm — DriftSense runs a compile-check on the shared bytes, backs up the current file on each target, writes, verifies the SHA post-write, and logs everything to RESTORE_LOG.
Safety guardrails
  • Compile-check preflight once on the shared bytes — blocks the whole batch if the source has a syntax error, unless you tick "force override"
  • Path safety: target must sit under the target monitor's scan_path — can't broadcast into /etc/passwd
  • Per-target backup file written before overwrite: <path>.drift_restore_backup_<epoch>
  • SHA verify post-write on every target; mismatches fail the row (backup still safe)
  • Every attempt — success or fail — lands in RESTORE_LOG for the audit trail

Not what you want? To restore a file to an earlier version on the same site, use File biography → pick a moment → Restore. To push an entire named release back to production, use Named releases → "Restore all pinned to this stable version".

Source: /var/www/vhosts/webstls.com/httpdocs/TEMPLATES/webstls_optimization.html
From WebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com) · blob SHA 4834eb5f191d600ccbf41934bda5a5f6394152bff3b1124058f666564e0fba1d
Targets
Pick the monitors that should receive this file. Target path defaults to the source basename inside each monitor's scan_path — override per-row if needed. The source monitor is excluded by default (broadcasting to yourself is a no-op).
 MonitorKindTarget path
DriftSense self-monitor on local local
PTMatrix (ptmatrix.3dshawn.com) on local local
AffSoft (affiliate.3dshawn.com) on local local
ShopCart (shop.3dshawn.com) on local local
RePricer (repricer.3dshawn.com) on local local
ABForge (abforge.3dshawn.com) on local local
ContactForge (crm.3dshawn.com) on local local
Meta-Admin (admin.3dshawn.com) on local local
SSH-agent watch: /etc/cron.d on localhost-ssh-agent ssh_agent
WebSTLs /httpdocs (SSH agent) on WebSTLs (webstls.com) source ssh_agent
Confirm broadcast
Preflight compile-check runs once on the source bytes before any write. If it fails, tick "force override" to broadcast anyway.
Cancel