Staging creates a separate working copy for testing updates and changes before applying them to the production website. It is available only for supported applications and configurations; Softaculous does not currently support its staging feature for WordPress multisite.
Create a staging copy
- Back up the live site and confirm you have enough disk and database capacity for a second copy.
- Open All Installations in Softaculous and choose Stage beside the correct application.
- Choose a separate destination domain or directory and review the database details. Do not select the live site's existing location.
- Click Stage Installation and wait for confirmation.
- Restrict access to the staging site and review its email, payment, webhook and scheduled-task integrations before testing. A copy may contain production customer data and working integration credentials.
- Test the intended changes without assuming that a search-engine visibility setting makes the copy private.
Be careful with Push to Live
Push to Live can overwrite production files and database data. Replacing the live database with an older staging copy can discard new orders, registrations, comments or edits. Back up the current live site first, review the available Default or Customize choices, and plan exactly which data should change. If the production site has continued receiving data, ask your developer or support to review the deployment plan before pushing.
Staging is not a substitute for an independent backup. If Stage or Push to Live is unavailable, do not try to force it by reinstalling the application.
Sources: Create Staging and Push to Live.
