ShoalStack is now
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.
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.
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.
Each environment keeps its own gateway address and deployment history, so you can see which version runs in staging and which runs in production.
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.
Run testing on managed hosting and production in your linked Google Cloud organization. Each linked environment gets its own Google Cloud project.
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.
Try the new setting on the staging graph first. Production keeps running the version your users have.
Deploy staging, and send its gateway address to the reviewer. They see the release before your users do.
Give production its own API keys and database. Tests in other environments do not use its keys or data.
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.
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.
Attach the website source to the container on the Development graph, and deploy it. Use this environment for the daily edits to the website.
Press Create again, and name the environment Staging. Attach the source with the content release to its container. Development does not change.
In Staging, press Deploy. When the deployment history shows succeeded, the reviewer can open the content release at the Staging gateway address.
Every environment works the same way, so what you learn in development also applies in production. The pages below cover the graph you build, the deployment that runs it, and its logs.
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.
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.