ShoalStack is now

platform201
Safer Changes Before Release

Environments for Development,
Staging, and Production

In platform201, each of them keeps its own graph, variables, gateway address, and deployment history. Add another from one short form, or clone one that already works.

developmentstagingproductionstagingGatewayContainerDatabaseContainer variablesAPI_URLstaging.acme.devLOG_LEVELinfoVersionv1.5DeployLivedevelopmentGatewayContainerAdd nodeContainer variablesAPI_URLdev.acme.devLOG_LEVELdebugVersionv1.6DeployDraft

Set Up Environments
That Stay Apart

A database you add to staging, or an API key you change there, does not reach production. A new environment also starts with a gateway and a container, so you do not start from an empty graph.

Create One Environment per Purpose

Name each environment for its job, such as Staging, Testing, or a client preview. There are no fixed types, so the list fits your release process.

stagingGatewayContainerEnvironmentsdevelopmentstagingproductionNew environmentstaging

Know Which Version Runs Where

Each environment keeps its own gateway address and deployment history, so you can see which version runs in staging and which runs in production.

staginghttps://staging.acme.devAPIv1.5Last deploy2 min agoproductionhttps://acme.devAPIv1.4Last deploy3 days ago

Reuse and Share What You Built

Create an environment as a clone of one you already have. On the Pro plan, you can also invite team members to work on the same environments.

stagingGatewayContainerClone environmentFromstagingNametestingShared withAlex RiveraCloneCloned

Choose Where Each Environment Runs

Run testing on managed hosting and production in your linked Google Cloud organization. Each linked environment gets its own Google Cloud project.

testingContainerDatabaseNew environmentNametestingCloud providerGoogle CloudHostingManagedUse my linked Google Cloud org

Reasons to Add a Second Environment

A project usually needs a second environment for one of the three reasons below. Each reason uses a different part of a platform201 environment: its graph, its gateway address, or its variables.

stagingMAX_UPLOAD_MB5050200productionMAX_UPLOAD_MB50

A Risky Configuration Change

Try the new setting on the staging graph first. Production keeps running the version your users have.

Gatewaystaging.acmeAddressReviewerusers

A Review Before Release

Deploy staging, and send its gateway address to the reviewer. They see the release before your users do.

productionstagingAPI keysAppDatabase

Production Keys and Data

Give production its own API keys and database. Tests in other environments do not use its keys or data.

Example Use Case:
Staging Environment for a Site

A documentation website shows the idea with few parts. You create Development for daily work, and then Staging, where a reviewer can read a content release before it goes live.

1

Create Development First

Open your website's project in platform201, or create one. Press Create to add an environment named Development. Its graph shows a gateway and a container.

2

Attach the Website Source

Attach the website source to the container on the Development graph, and deploy it. Use this environment for the daily edits to the website.

3

Create the Staging Environment

Press Create again, and name the environment Staging. Attach the source with the content release to its container. Development does not change.

4

Deploy Staging for Review

In Staging, press Deploy. When the deployment history shows succeeded, the reviewer can open the content release at the Staging gateway address.

Begin With Development, Add Staging Later

Build the first environment on the free plan, which includes three projects. When the work needs a place to test or review, move to a plan with unlimited environments and add Staging.

FAQ

A staging environment is a separate copy of an application for testing and review before a release. A team can check a change there without affecting the live version that users see. In platform201, staging is an environment that you create and name yourself, with its own graph, variables, and deployment history.