Safe updates
Production sites update through SiteUpdater and managed release ZIPs (including cms_release from MCP). The goal is predictable deploys on shared hosting — backup first, apply the package, verify the site.
Platform Core updates ship from github.com/iia3uk/jasefly. Domain package ZIPs come from Jasefly-Modules (15 first-party modules).
- Backup — Snapshot files and database before applying any update ZIP.
- Apply — Upload/apply the release via admin updater or MCP cms_release pipeline.
- Migrate — Run pending migrations if the release includes schema changes.
- Verify — Hard-refresh the admin (Ctrl+F5), smoke public pages, check diagnostics.
What the updater protects
Operational realities of the framework.
- Asset prune — Stale hashed frontend files are cleaned after a successful update.
- Module quarantine — A broken ZIP module can isolate instead of killing the API process.
- Config stays local — Hosting secrets are not overwritten by the public release package.
Need the install baseline?
Core install ZIP on GitHub · domain packages in Jasefly-Modules.