> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.flyinghost.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Create a staging site in FlyingHost

A staging site is a separate copy of your live WordPress site for testing updates, configuration changes, or fixes. Changes you make on staging leave the live site unchanged.

## Create and open a staging site

1. Sign in to FlyingHost Cockpit as an organization admin and open the ready live site you want to copy.
2. In the site header, select **+ Staging** next to **Live**.
3. Select **Create staging** to confirm. Wait for Cockpit to finish copying the site.
4. Use **Live** and **Staging** in the site header to switch environments. Open the staging site using its temporary FlyingHost address.

![Confirmation dialog for creating a staging copy of Harbor Coffee](https://storage.crisp.chat/users/helpdesk/website/-/3/5/a/3/35a3c3ffe31dc000/create-staging_1ljy57w.png)

![Staging selected in the site header, with a banner identifying the staging copy](https://storage.crisp.chat/users/helpdesk/website/-/3/5/a/3/35a3c3ffe31dc000/staging-environment_17yjc89.png)

Each live site can have one staging copy. If one already exists, selecting **Staging** opens it. Custom domains are available on the live site.

## Test changes and apply them to the live site

Confirm that the header says **Staging** before making changes. When testing integrations, use test settings for payments and email where available.

Changes made in staging do not automatically sync to live. For a plugin update or settings change you can repeat, create a backup of the live site, switch to **Live**, and apply the tested change there. If the change involves moving files or database content, ask FlyingHost support about the safest way to move it. On an active store or membership site, avoid replacing the live database with the staging copy, because it may overwrite newer orders or account changes.