ZuloOne
English
CabinetAccount
Sign in
Menu

Deploy a Test environment

Updated

Test is where a package proves itself before Production. You can also deploy Development, where people write code and the workspace can be mirrored onto a laptop.

Note

Production is never deployed from this page. Its address is already <tenant>.zulo.one. A Test or Development address is <tenant>-<name>.zulo.one. The plan caps how many stands you may have beside Production.

The portal is lcp.getzulo.com. Its buttons are in English.

How to#

To deploy a Test environment, sign in at lcp.getzulo.com and open the tenant. In the left menu press + Deploy an environment.

Fill Name (lowercase letters, digits, and dashes). The prefix is the tenant slug; the address will be that slug, a dash, then this name.

Under Kind:

  • Test — where a package proves itself before production. Refreshed from production, not written on.
  • Development — where code is written; the workspace can be mirrored onto a laptop.

Under Data:

  • Empty — a clean ZuloOne.
  • A copy of production — today's data. Mail and outbound integrations are switched off in the copy, so it never writes to your customers or the tax office.

If the form offers Then install what production runs, tick it on an empty environment so Test starts on the same packages as Production. A copy of production has them already.

Press Deploy. Wait until the environment is Active on Environments. Sign in at the new address and try the change, then ship the package.

The plan allows a fixed number of environments beside Production. If they are all in use, the page says so: delete one, or redeploy it, before deploying another.

On a Test or Development page you can later Refresh from production (replaces its data with today's Production, mail still off), Rebuild clean (wipes business data, keeps users and settings, snapshot first), or Delete (removes the stand, its data, and its address). Type the environment's slug to confirm each of those. Production has none of those buttons.

Example

Tenant acme. Name test. Kind Test. Data A copy of production. Deploy.

People open acme-test.zulo.one. Mail does not leave. A package is installed here before Production.

Tip

Development is for writing. Test is for proving a package. Do not use Development as the Ready evidence — the install step on the package says a Development install changes nothing for the mark.

If the command refuses#

What you see What to do
The plan allows n environment(s) beside production, and they are all in use Open an unused Test or Development, Delete it (type its slug), then Deploy again. Or raise the plan.
Name validation error Use lowercase letters, digits, and dashes only.
Production is missing from this form That is intended. Production is the tenant's own name and is not created here.
The environment was stopped because the plan no longer covers it Raise the plan, or delete another Test or Development, before the date on the red notice.

See also

Was this page helpful?