> ## Documentation Index
> Fetch the complete documentation index at: https://docs.godizzy.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments Workflow

> The recommended GoDizzy workflow is to build in development, then copy into shared production when ready.

The GoDizzy workflow is simple:

1. build in **development**
2. validate what you need
3. copy into **production** when ready

## Environment roles

<CardGroup cols={2}>
  <Card title="Development" icon="user">
    Private sandbox for the creator. Safe for risky experiments and rapid iteration.
  </Card>

  <Card title="Production" icon="globe">
    Shared environment for teammates and live traffic.
  </Card>
</CardGroup>

## Recommended workflow: development → production

<Steps>
  <Step title="Build in development">
    Create a collection in your development environment, add routing rules, and iterate until behavior is correct.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Copy the collection into production">
    Open the collection, click **Copy Collection**, and choose **Production**.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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

| Situation                                 | Environment                    |
| ----------------------------------------- | ------------------------------ |
| First draft of a new rule                 | Development                    |
| Risky failure simulation                  | Development                    |
| Shared traffic or teammate-visible config | Production                     |
| Rollback of a shared rule                 | Production 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.