Managed EmDash updates
Included at launch · Currently being tested
Updates without crossing your fingers.
DashHarbor treats an EmDash update as a controlled site operation, not simply a new deployment. The site is protected first, updated, checked and only then accepted as the new working release.
Safe update lifecycle
Protect. Update. Verify. Promote or roll back.
- 1. Verify the supported update.DashHarbor starts from a release that has been approved for the managed platform.
- 2. Create pre-update protection.The existing website state is protected before the update mutates it.
- 3. Apply the update.The EmDash release, required migrations and the managed website deployment are updated together.
- 4. Check the result.DashHarbor verifies the public website, editor, content and media before accepting the release.
- 5. Promote or recover.A verified release becomes current. A failed mandatory check triggers recovery to the previous protected state.
Automatic rollback
A failed update should not become your problem.
If a required check fails after the website has been changed, DashHarbor can restore the protected pre-update state rather than leaving the site on a partially completed release.
Public availability
Keep serving the last known good website.
Consistency-sensitive operations can temporarily pause writes while DashHarbor continues serving the previously verified public website to visitors. The editor may pause briefly without turning that protection window into visible public downtime.
Planned update policies
Control the policy without managing arbitrary versions.
DashHarbor plans simple policies such as automatic safe updates or notification before updating. The intention is to give customers useful control without turning software-version selection into another hosting administration task.
Read the EmDash updates guideManaged EmDash
Part of the platform around your website.
You manage your website in EmDash. DashHarbor manages the hosting, deployment and operational layer underneath it.