Starter projects
The Starter plan architecture has four environments:
-
Integration—The integration environment provides two testable environments. Each environment includes an active Git branch, database, web server, caching, some services, environment variables, and configurations.
-
Staging—As code and extensions pass your tests, you can merge your
integration
branch to the Staging environment, which becomes your pre-production testing environment. It includes thestaging
active branch, database, web server, caching, third-party services, environment variables, configurations, and services, such as Fastly and New Relic. -
Production—When code is ready and tested, all code merges to
master
for deployment to the production live site. This environment includes your activemaster
branch, database, web server, caching, third-party services, environment variables, and configurations. -
Inactive—You have an unlimited number of inactive branches.
Pro projects
The Pro plan architecture has a global master
with three environments:
-
Integration—The integration environment provides a testable environment that includes a database, web server, caching, some services, environment variables, and configurations. You can develop, deploy, and test your code before merging to the Staging environment.
- Inactive—You can have an unlimited number of inactive branches based on the
integration
environment, but only one active branch (not includingintegration
).
- Inactive—You can have an unlimited number of inactive branches based on the
-
Staging—The staging environment is for pre-production testing and includes a database, web server, caching, third-party services, environment variables, configurations, and services, such as Fastly.
-
Production—The production environment includes a three-node, high-availability architecture for your data, services, caching, and store. Production is your live, public store environment with environment variables, configurations, and third-party services.