Skip to main content
The GoDizzy workflow is simple:
  1. build in development
  2. validate what you need
  3. copy into production when ready

​
Environment roles

Development

Private sandbox for the creator. Safe for risky experiments and rapid iteration.

Production

Shared environment for teammates and live traffic.
1

Build in development

Create a collection in your development environment, add routing rules, and iterate until behavior is correct.
2

Validate using the generated collection URL

Point your local tests, agent, or debugging client at the development collection URL and confirm the rules behave as expected.
3

Copy the collection into production

Open the collection, click Copy Collection, and choose Production.
4

Use the production copy for shared or live traffic

The production copy is independent from the development original. Further edits in one do not automatically change the other.

​
What gets copied

Copying a collection duplicates:
  • collection metadata
  • routing rules, including the default rule
  • current mock response configuration
  • current proxy shaping configuration
Each copied entity then evolves independently.

​
When to use each environment

SituationEnvironment
First draft of a new ruleDevelopment
Risky failure simulationDevelopment
Shared traffic or teammate-visible configProduction
Rollback of a shared ruleProduction via version history

​
Multiple collections per environment

You can keep multiple collections in one environment. Each collection gets its own generated GoDizzy URL and its own routing rules.