Free Rotator Script guide

Updating

Before replacing files

  1. Download the core Admin backup.
  2. Make a server-side backup of config.php, the entire storage/ directory, uploads/, keys/, and mods/.
  3. Record the current core version and active MOD versions.
  4. Keep the previous release ZIP available for rollback.

Apply the core update

Open Admin → Updates, choose Check Home Base for updates, review the signed release, then choose Back up and install. The updater verifies the Home Base RSA signature, PHP requirement, HTTPS download, ZIP structure, file limits, and SHA-256 checksum before changing a core file. It stages files privately and creates a persistent file-level rollback first.

The updater never overwrites config.php, storage/, uploads/, keys/, mods/, or local release/private tooling. If a file cannot be replaced, it automatically restores the prior core files. After installation, verify the homepage, rotator, Admin, lead flow, and MOD pages before removing server backups.

Manual fallback

If the host blocks outbound HTTPS, cURL, ZIP, or PHP file writes, upload the new release files without overwriting config.php, storage/, uploads/, keys/, or mods/. Never replace a live installation by deleting its whole directory first. Recheck host permissions and sign in to Admin.

Older configurations that do not define admin_username inherit admin; add an explicit username when convenient. Open MOD Manager, refresh entitlements and compatibility, and apply MOD updates only after the core is stable. A core release does not contain purchased MOD packages or Home Base secrets.

Verify and roll back

Repeat the important checks in FRESH_DOMAIN_ACCEPTANCE.md: homepage, /demo/, Admin login, lead confirmation, protected download, unsubscribe, backup, and active MOD pages. If something breaks, restore the previous file copy and preserved state. Use Admin restore only for a compatible core backup and never as a substitute for backing up MOD databases.

Clean release expectations

An official release must install with empty JSON seeds, no credentials, no leads, no mail logs, no private backups, no purchased MOD code, and no Home Base owner tooling. It should include the public MOD verification key and customer MOD Manager.

Free core versus Home Base

Installable updates are built from the release manifest. Do not copy the production Home Base directory over a customer installation, and never move private signing keys, payment credentials, customer records, or release databases into a public web package.