CoreCluster · Build

Environments

Give each site staging and development copies, each with its own files, database, address and SSH port.

Start free for 30 days ← Back to CoreCluster
manage.corefinity.com/managed-clusters
Environments 3
Each one is its own copy: files, database, address, SSH port.
Clone…New environment
EnvironmentAddressSizeDeploysSnapshots
Production
production		 www.marrowtide.co.uk
certificate ready		 M main
deploys on push		 Daily Open ↗
Staging …-staging-brindlewyck.cfstack.io
password-protected · noindex		 S release/october Off Open ↗
Push to live…
Development …-dev-brindlewyck.cfstack.io
Cloning from Staging · step 3 of 5		 S feature/new-menu Off

Snapshots are incremental, daily by default and down to hourly; switch them on or off per environment.

{  How it works  }

Environments, step by step

  1. 1

    Create an environment

    Name it, choose Staging or Development and a size, and start empty or from a copy.

    manage.corefinity.com/managed-clusters
    Create environment marrowtide.co.uk
    Name Staging Hostname marrowtide-co-uk-staging-brindlewyck.cfstack.io noindex
    Size SML Same as Production
    Role
    StagingFor review before changes reach the site.
    DevelopmentFor building; nothing visitors should see.
    Start from
    EmptyNothing copied
    A copy of ProductionFiles and database
    A Git branchDeploys on push
    OnPassword OffSnapshots HeldEmail
    CancelCreate environment
  2. 2

    Work on a protected copy

    Staging and development ask for a password, stay out of search engines and hold outgoing email.

    manage.corefinity.com/managed-clusters
    Environments 3
    Each one is its own copy: files, database, address, SSH port.
    Clone…New environment
    EnvironmentAddressSizeDeploysSnapshots
    Production
    production    		 www.marrowtide.co.uk
    certificate ready    		 M main
    deploys on push    		 Daily Open ↗
    Staging …-staging-brindlewyck.cfstack.io
    password-protected · noindex    		 S release/october Off Open ↗
    Push to live…
    Development …-dev-brindlewyck.cfstack.io
    Cloning from Staging · step 3 of 5    		 S feature/new-menu Off

    Snapshots are incremental, daily by default and down to hourly; switch them on or off per environment.

  3. 3

    Clone between environments

    Copy files, the database or both onto another environment. A safety snapshot of the target comes first.

    manage.corefinity.com/managed-clusters
    Clone Production to Staging marrowtide.co.uk
    Productionwww.marrowtide.co.uk
    →
    Stagingmarrowtide-co-uk-staging-brindlewyck.cfstack.io
    What to copy Files and databaseDatabase onlyFiles only

    Files 1.2 GB · database 240 MB · about 3 minutes. Staging’s current contents (0.9 GB) are replaced.

    Take a safety snapshot of Staging firstIf the copy fails, Staging is restored from it automatically.
    • Addresses in the copy are rewritten to marrowtide-co-uk-staging-brindlewyck.cfstack.io.
    • The WordPress admin password on Staging is reset and shown once.
    • Staging is unavailable for a few minutes while the data is copied.
    Cancel Clone to Staging
  4. 4

    Push to live

    Type the domain to confirm. Production is snapshotted first and restored on its own if the push fails.

    manage.corefinity.com/managed-clusters
    Push Staging to live on marrowtide.co.uk
    Push to live

    !This replaces the live site at www.marrowtide.co.uk with Staging’s files and database.

    Take a safety snapshot of Production firstAlways on for a push. If it fails, Production is restored and the live site is as it was.
    • Production is stopped for a few minutes while its data is replaced.
    • Addresses are rewritten to www.marrowtide.co.uk.
    • Production keeps its own crons, email and domain settings.
    • A new WordPress admin password is shown once when the push is done.
    Type marrowtide.co.uk to confirm marrowtide.co.uk
    Cancel Push to live on marrowtide.co.uk
manage.corefinity.com/managed-clusters
Create environment marrowtide.co.uk
Name Staging Hostname marrowtide-co-uk-staging-brindlewyck.cfstack.io noindex
Size SML Same as Production
Role
StagingFor review before changes reach the site.
DevelopmentFor building; nothing visitors should see.
Start from
EmptyNothing copied
A copy of ProductionFiles and database
A Git branchDeploys on push
OnPassword OffSnapshots HeldEmail
CancelCreate environment
manage.corefinity.com/managed-clusters
Environments 3
Each one is its own copy: files, database, address, SSH port.
Clone…New environment
EnvironmentAddressSizeDeploysSnapshots
Production
production		 www.marrowtide.co.uk
certificate ready		 M main
deploys on push		 Daily Open ↗
Staging …-staging-brindlewyck.cfstack.io
password-protected · noindex		 S release/october Off Open ↗
Push to live…
Development …-dev-brindlewyck.cfstack.io
Cloning from Staging · step 3 of 5		 S feature/new-menu Off

Snapshots are incremental, daily by default and down to hourly; switch them on or off per environment.

manage.corefinity.com/managed-clusters
Clone Production to Staging marrowtide.co.uk
Productionwww.marrowtide.co.uk
→
Stagingmarrowtide-co-uk-staging-brindlewyck.cfstack.io
What to copy Files and databaseDatabase onlyFiles only

Files 1.2 GB · database 240 MB · about 3 minutes. Staging’s current contents (0.9 GB) are replaced.

Take a safety snapshot of Staging firstIf the copy fails, Staging is restored from it automatically.
  • Addresses in the copy are rewritten to marrowtide-co-uk-staging-brindlewyck.cfstack.io.
  • The WordPress admin password on Staging is reset and shown once.
  • Staging is unavailable for a few minutes while the data is copied.
Cancel Clone to Staging
manage.corefinity.com/managed-clusters
Push Staging to live on marrowtide.co.uk
Push to live

!This replaces the live site at www.marrowtide.co.uk with Staging’s files and database.

Take a safety snapshot of Production firstAlways on for a push. If it fails, Production is restored and the live site is as it was.
  • Production is stopped for a few minutes while its data is replaced.
  • Addresses are rewritten to www.marrowtide.co.uk.
  • Production keeps its own crons, email and domain settings.
  • A new WordPress admin password is shown once when the push is done.
Type marrowtide.co.uk to confirm marrowtide.co.uk
Cancel Push to live on marrowtide.co.uk
{  What you can set  }

Options and limits

Everything here is per site or per environment, from the panel, with every change in the activity log.

Roles
Production, plus as many Staging and Development environments as the cluster has room for.
Start from
Empty, a copy of another environment, or a Git branch that deploys on push.
What to copy
Files and database, database only, or files only. A preview shows sizes and time first.
Clone to
Another environment on the cluster, a new environment, a new site, or production.
Off production
Password protection on, search engines blocked, scheduled tasks off and outgoing email held.
Snapshots
Daily on production by default, down to hourly, kept 30 days. Off on staging and development until you turn them on.
Addresses
Each has its own address, like marrowtide-co-uk-staging-brindlewyck.cfstack.io, and SSH port.
Deleting
A final snapshot is taken first and kept 7 days. Production goes only with the site.

Questions about environments

Not without the password. Staging and development are password-protected from the start, every address tells search engines not to index it, and outgoing email is held, so customers receive nothing.

Production gets a safety snapshot before anything changes. If the copy fails, production is restored from it automatically and the live site is as it was. Production is offline for a few minutes during a push, so pick a quiet time.

Yes, the same way sites do. Each one uses CPU, memory and disk, and new ones wait when the cluster passes 90% of any of the three. There is no fixed limit on how many you create.

← PreviousCreate a site Next →WordPress tools
Every walkthrough Back to CoreCluster →
Build
Launch
Ship
Protect
{  CoreCluster  }

See environments on your own cluster

Tell us how many sites you run and on what. An engineer sizes a cluster with you and shows you the panel on a live one.

By sending this message you agree to our Privacy Policy .