#DEVDOCS BIG COMMERCE UPGRADE#
#DEVDOCS BIG COMMERCE PRO#
#DEVDOCS BIG COMMERCE CODE#

Instead, you push code changes from the integration branch to the staging branch. You cannot create a branch from the staging branch. See Deployment workflow and Test deployment.Īfter launching the Production site, use the Staging environment primarily to test patches for Production-critical bug fixes. Test new builds instead of patching in ProductionĬustomize cron configuration and test cron jobs Performance testing with Fastly caching enabled Regression testing against production data For example, you can use the Staging environment to complete the following tasks: The Staging environment matches the Production architecture and is designed for UAT, content staging, and final review before pushing features to the Production environment. This environment, which is hosted on dedicated IaaS hardware, includes all services, such as Fastly CDN, New Relic APM, and search. The Staging environment provides a near-production environment to test your site. See the Integration Environment request article in the Adobe Commerce Help Center for details.

#DEVDOCS BIG COMMERCE UPGRADE#

If you need a larger Integration environment for testing and development, request an upgrade to Enhanced Integration environments. Projects provisioned before Jhad multiple, smaller Integration environments. You cannot restore the Integration database from Production or Staging The integration environment architecture does not match the Production and Staging architectureĭo not use the integration environment for development testing, performance testing, or user acceptance testing (UAT)ĭo not use the integration environment to test B2B for Adobe Commerce functionality Test critical workflows on key pages like Home, Category, Product Details Page (PDP), Checkout, and Adminįor best performance in the integration environment follow these best practices:ĭisable cron jobs and manually run as neededįastly CDN and New Relic services are not accessible in an integration environment For example, you can use the integration environment to complete the following tasks:Įnsure that changes to continuous integration (CI) processes are Cloud compatible Integration environments are designed for limited testing and development before moving changes to Staging and Production.

See Regional IP Addresses for a list of AWS and Azure IP addresses. Each environment includes a web server and database to test your site. The integration environment runs in a Linux container (LXC) on a grid of servers known as Platform as a service (PaaS). Use the integration environment branch to create new, active branches.ĭo not use the master environment for development, UAT, or performance testing Always push a copy of the Production code to the master environment so that you can debug the Production environment without interrupting services.ĭo not create a branch based on the master branch.

#DEVDOCS BIG COMMERCE PRO#

On Pro projects, the master branch provides an active PaaS environment with your Production environment. The following diagram shows the hierarchical relationship of the environments: Your project is a single Git repository with three, main environment branches for Integration, Staging, and Production. The following table summarizes the differences between environments:Īdobe also provides the Cloud Docker for Commerce solution for deploying to a local Cloud Docker environment so that you can develop and test Adobe Commerce projects. Production-Provides a single environment branch deployed to dedicated Infrastructure as a service (IaaS) containers.Staging-Provides a single environment branch deployed to dedicated Infrastructure as a service (IaaS) containers.This allows for up to two active branches deployed to Platform as a service (PaaS) containers. Integration-Provides a single environment branch, and you can create one additional, environment branch.Master-Provides a master branch deployed to Platform as a service (PaaS) containers.Include the URL of the storefront you will be making the request from as the allowed_cors_origin.Your Adobe Commerce on cloud infrastructure Pro architecture supports multiple environments that you can use to develop, test, and launch your store. It is a REST API request, so you will need to copy and paste your API credentials. We'll use Request Runner for making an initial request to obtain a Storefront API token. To make your first requests in a browser with the Storefront APIs, see the step-by-step tutorial Working with Storefront Cart and Checkout APIs. To view sample JSON request bodies for each REST API resource, see the API Reference for that resource. You can import many of our API Specification Files into Postman (opens in a new tab) (or any other tool that can import Open API Specification (opens in a new tab) files) to try out endpoints and view responses. Click send request and the response will open in a split window. Save and you'll see the send request link above GET.

Devdocs big commerce