StagingPro comes with three license tiers.
For the Standard Tier two Staging Environments are provisioned in addition to the Production Store.
For the Plus Tier, three Staging Environments are provisioned in addition to the Production Store.
For the Premium Tier five Staging Environments are provisioned in addition to the Production Store.
The suggested best practice for naming the staging environents is as follows:
1st Staging website: Staging
2nd Staging website: UAT
3rd Staging website: Integration1
4th Staging website: Integration2
5th Staging website: Integration3
Before you start using StagingPro, you must plan your environments so it is will be setup correctly .in StagingPro
To do this, prepare a tabulation of the environments assigned for use with StagingPro for ease of reference as follows:
Proposed environment name | Store Hash ID | Description | Proposed store link/ | Link approval |
|---|---|---|---|---|
Production | a123b321 | This is the live store | - | Approve (SP) link on Production |
Staging | a432c456 | This is the pre-deployment store for smoke tests | Staging ⇔ Production (SP) | Approve (US) link on Staging |
UAT | a723d367 | This is the user acceptance store configured for production builds | UAT ⇔ Staging (US) | Approve (UI) link on UAT |
Integration | b648ce56 | This is for system integration checksUAT ⇔ Integration (UI) |
Doing so will help you to determine:
The correct environment names How to link your environments correctlybefore linking/association tasks
Distinguish between production and non-production environments (as any migration tests must happen in non-production environments first)
To view our onboarding steps, please access the following article → StagingPro Onboarding