Testing environments

Within WebSonic.io, there are two environments for you to test configuration - Staging and Production.

Staging environment

Staging environment allows you to test any configuration version on your website without affecting live production website.

Steps to test a configuration version on staging:

  1. Create a new configuration version.

  2. Publish it on staging environment. This configuration version will be saved and locked. You won't be able to edit this version. For making any other changes, you can clone this version and edit.

  3. For testing on staging, add a request header x-ws-staging with value true. Use Mod Header plugin for Chrome to add/override request headers.

  4. The deployment will take up to 10 minutes, and you cannot reverse this action.

Once a configuration is published, you will be able to see the active version on the configuration page.

Production environment

Once you have tested a configuration version on staging environment and ready to go live, publish that version to production.

Always test configuration on staging first Publishing a configuration version directly to production without first testing on staging can break your live website.

Steps to publish a configuration version on staging:

  1. Make sure you have tested the configuration on staging environment first.

  2. Click on publish to Production.

  3. This configuration version will be saved and locked. You won't be able to edit this version. For making any other changes, you can clone this version and edit.

  4. The deployment will take up to 10 minutes, and you cannot reverse this action.

Congratulations 🙌 You have successfully published your changes on the live website.