Staging and “Push live”

A second copy of your app on the same server, at its own address, with its own settings. Each database 1ClickOps runs for your live app gets its own staging copy too, with its own password.

Open your app, then Versions and staging, and find Updates and staging. Choose what staging’s database starts with, then press Create staging.

• A copy of your live data. The copy stays on your server, but because anyone with the link can open staging, real customer records and real logins are reachable too.
• Nothing (empty). Use this if staging should never hold real customer data.

A database you only linked cannot be copied. Give staging its own connection link, or tick the box that lets staging use your live database. With that box ticked, anything you test on staging changes real data.

Settings are copied from your live app. If one of them can still reach a live database, the card warns you and names the setting.

A new push no longer goes straight to your live site. It waits on staging. Your live site changes only when you press Push liveon staging's Overview.

Exactly the version you checked on staging. It is identified precisely, so code pushed a moment later does not slip in with it.

• It is offered for staging’s newest version, and only if that version deployed successfully.
• Your live app’s server confirms it received exactly that version. If it reports anything else, the push stops.
• The new version starts beside the current one. Visitors are switched over only if it is healthy. If it is not, your site stays as it is.

• First, each live database that 1ClickOps runs is backed up. If a backup fails, the push stops before anything changes.
• If you saved a command that updates your database tables, the confirmation offers Update the live database. The command runs inside the new version before visitors reach it. If it fails, the push stops and your site stays on the current version.
• Push live never copies staging’s data over your live data. It moves code and runs your update command. What your customers did on the live site stays.
• If a push fails after the update command has run, the update may already have been applied. The backup from the first step is there for that. See Backups and restore.

Remove staging deletes the staging copy of your app and the staging database with everything in it. Your live site and live data are not touched. Pushes go straight to your live site again.