Pushing a staging site to production does not break HomeRunner syncing.
Why this happens. Each site registers its own webhooks with HomeRunner under its own URL. When a staging copy registers webhooks, it adds a second registration alongside the live site’s rather than replacing it. While both sites are registered, both receive property and booking updates.
Steps around a staging-to-production push.
- Before pushing, on the live site go to HomeRunner > Sync and click Check Webhooks. If any are missing, click Register Webhooks. You can do the same on the staging site if you want it kept current while you work on it.
- Push staging to production as usual. Property and booking data is not a concern either way, since HomeRunner keeps both sites current automatically and continues updating the live site after the push.
- After the push, on the retired staging site go to HomeRunner > Sync and click Delete Webhooks. This removes only the staging site’s own registration and leaves the live site’s registration intact. It stops the staging copy from continuing to receive live property and booking updates once it is no longer needed.
A caution about the hosting push. This concerns the hosting push itself rather than HomeRunner. A full staging-to-live push replaces the live database with the staging snapshot, so any content added directly on the live site after the staging copy was made (page edits, new media, form entries) is overwritten. Review or re-apply those changes before pushing.