A CanaryWP testing environment is an isolated WordPress copy used to evaluate changes away from the source site.
Source site versus testing environment
Source WordPress site
The original website.
Archive
A backup used to build a CanaryWP copy.
CanaryWP testing environment
The isolated copy restored or provisioned by CanaryWP.
Instance
The individual managed environment representing that copy.
Why this separation matters
The primary purpose of CanaryWP is to give you a place where potentially risky work can be evaluated without performing that work directly on the source site.
For example, you can test:
- Plugin updates
- Theme updates
- WordPress upgrades
- PHP upgrades
- Database operations
- Configuration changes
- Functional behavior
- Visual changes
Environment lifecycle
An environment can pass through several lifecycle states.
Creating
CanaryWP is provisioning or restoring the environment.
Running
The environment is available for normal use.
Stopped
The environment still exists but its active compute is paused.
Error
The most recent lifecycle operation requires investigation.
Destroying
CanaryWP is removing the environment and its owned resources.
Stopping versus deleting
Stopping an environment is temporary.
Deleting an environment is destructive.
If you only want to pause work, use the available stop/pause lifecycle control rather than deletion.
Source-site safety
Deleting or stopping a CanaryWP instance should affect the CanaryWP environment, not the original WordPress source.
This separation does not eliminate the need to check your target before performing operations. Always confirm that you are working on the CanaryWP URL.
How to confirm your environment
Before performing destructive maintenance:
- Check the instance name.
- Check the URL.
- Check the workspace.
- Confirm that the environment is the intended CanaryWP copy.
- Review the source relationship if one exists.
Moving successful changes to production
CanaryWP validates changes; it should not be treated as an automatic substitute for your existing production release process unless a specific production workflow explicitly supports that action.
After a successful CanaryWP test, use your normal deployment or WordPress maintenance procedure to apply the approved change.