Starter develop and deploy workflow

Everything in Magento Commerce (Cloud) is Git-driven. Your project is a Master Git branch cloned from a Magento 2 repository. Every active Git branch has an associated full environment. Depending on your Magento Commerce (Cloud) plan subscription, your deployment workflow may differ.

The general workflow for all development and deployment includes:

• Push code to the remote Git branch
• Build and deploy processes run
• The environments updated with code, services, and configurations

The Starter plan gives you four active environments, including a master environment for your Production server. You have the option to use the remaining three active branches any way you want.

We recommend creating a Staging branch for fully testing your code, extensions, integrations, and data as a near-production environment. This branch includes all services and features of your Production environment. The remaining branches you can create from staging and use for all development, easily merging work up through staging then master.

Every active environment gives you the Magento and branch code installed and deployed, configurable services, and a database. Only the Production and Staging environments have full services including Fastly and New Relic.

The following diagram details the branch and environment relationships:

You can manage all of your environments including Production and Staging directly through the Project Web Interface, through the store and Admin panel using provided URLs, and using SSH and the Magento Cloud command-line.

Starter environments and branches

For your environments, we recommend deploying and testing following a Development > Staging > Production workflow.

• Production environment (live site) is your master Git branch with an associated full environment with all services
• Staging environment is a Git branch we recommend you create called staging, to receive full services matching Production
• Integration environments include two active branches we recommend created from staging

For your branches, you can follow any methodology. One example follows an Agile methodology such as scrum to create branches for every sprint.

From each sprint, you can have branches for every user story. All the stories become testable. You can continually merge to the sprint branch and validate that on a continuous basis. When the sprint ends, there is no testing bottleneck, and you can just merge to master and put the whole sprint into production.

For detailed information, see Starter architecture.

Development workflow

Development and deployment on Starter plans begins with your initial project. You create your project with the “blank site”, which is a Magento Commerce (Cloud) template code repo with a fully prepared store. This creates a master branch of Git code in your Production environment.

The full process involves:

• Clone and branch from Master for Staging and development branches
• Develop code and install extensions locally in a branch
• Configure your store and extension settings
• Generate configuration management files
• Push code and configuration to build and deploy to an environment

You also have a few optional steps to help develop and test your code and store data:

• Install sample data to your store
• Pull production store data down to environments

This process assumes you would have your local developer workspace set up. Feel free to read over this process even if your local isn’t ready.

Clone and branch

When you created your project, a master branch was cloned using the Magento Commerce (Cloud) Git repository. To start branching and working with code, you will need to clone the master to your local.

The format of the Git clone command is:

git fetch origin
git pull origin <environment ID>

The first time you start working in branches for your Starter project, you need to create a Staging branch. This sets up a Staging environment with a code branch matching the Production master branch and environment.

Next, create branches from staging to develop code, add extensions, and configure 3rd party integrations. Anytime you need to develop custom code, add extensions, integrate with a 3rd party service, work in a develop branch created from staging. You will have four active Integration environments available. When you push your an active branch of Git code, one of these Integration environments automatically deploys your code to test.

We walk you through the process when you set up your local.

The format of the Git branch command is:

git checkout <branch name>

The format of the Magento Cloud CLI branch command is:

magento-cloud environment:branch <environment name> <parent environment ID>

Develop code

It’s the time you have been waiting for…writing code. Using this base branch of Magento Commerce (Cloud) code, you can start installing extensions, developing custom code, adding themes, and much more.

We recommend using a branching strategy with your development work. Using one branch to do all of your work all at once might make testing difficult. For example, you could follow continuous integration and sprint methodologies to work:

• Add a few extensions and configure them with your first branch
• Push this code, test, and merge to Staging then Production
• Fully configure your services in services.yaml and add a theme
• Push this code, test, and merge to Staging then Production
• Integrate with a 3rd party service
• Push this code, test, and merge to Staging then Production

And so on until you have your store fully built, configured, and ready to go live. But keep reading, we have even better options for your store and code configuration!

Configure store

When you are ready to configure your store, have all code pushed to your Integration environment and access the Magento Admin. You should fully configure all store settings in the Integration environment Admin, not on your local. If you need the URL, see the Project Web Interface. The Store Admin URL is located on the branch page.

For the best information on configurations, we recommend reviewing Magento Commerce and your extension documentation. Here are some links and ideas to help you get kickstarted:

• Best practices for store configuration for specific best practices in the cloud
• Basic configuration for store admin access, name, languages, currencies, branding, sites, store views and more
• Theme for your look and feel of the site and stores including CSS and layouts
• System configuration for roles, tools, notifications, and your encryption key for your database
• Extension settings using their documentation

Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. For details, see Configure Magento Commerce.

Now you need to get these settings into your code. We have a helpful command to do this, keep reading.

Generate configuration management files

If you are familiar with Magento, you may be concerned about how to get your configuration settings from your database in development to Staging and Production. Previously, you had to copy down on paper or a file all of your configuration settings to enter them manually in another environment. Or you may have dumped your database and push that data to another environment.

Magento Commerce (Cloud) provides a set of two Configuration Management commands that export configuration settings from your environment into a file. These commands are only available for Magento Commerce (Cloud) 2.2 and later.

• php vendor/bin/m2-ece-scd-dump: Recommended. Exports only the configuration settings you have entered or modified from defaults into a configuration file.
• php bin/magento app:config:dump: Exports every configuration setting, including modified and default, into a configuration file.

The generated file is app/etc/config.php.

You will generate the file in the Integration environment where you configured Magento. We walk you through the process of generating the file, adding it to your Git branch, and deploying it.

Important notes on Configuration Management:

• Any configuration setting included in the file is locked from editing, or read-only, in the deployed environment. This is one reason we recommend using scd-dump.

  For example, we will have you install a module for Fastly in your development environment. You will only configure this module in Staging and Production. Using scd-dump keeps those default fields editable.

• This file can be long depending on the size of your deployment. The scd-dump command generates a far small file than app:config:dump.

An additional feature of this command is part of Magento Commerce (Cloud) 2.2. Any values determined to be sensitive data, like sandbox credentials for a PayPal module, will be generated into another configuration file called env.php in app/etc/. This file remains in the exact environment it is created without traveling with your code. You will not add this file to your code repository. You can also create environment variables with CLI commands in all Magento Commerce (Cloud) versions.

For more information, see Configuration Management.

Push code and test

At this point, you should have a developed code branch with a configuration file (config.local.php or config.php) ready to test.

Everytime you push code from your local environment, a series of build and deploy scripts run. These scripts generate new Magento code and deploy it to the remote environment. For example, if you are pushing a development branch from your local to the remote Git branch, a matching environment updates services, code, and static content.

You can directly access this environment with a store URL, Magento Admin URL, and SSH. These environments include a web server, database, and configured services. When ready, you can start deploying and testing in Staging.

For more information, see Deployment workflow.

Optional: Install sample data

If you need some example data when developing your store, you can install our sample data. This data simulates an active Magento store, including customers, products, and other data. This sample data works best with a “blank site” Magento Commerce (Cloud) template installation when creating your project.

We recommend installing sample data in your local installation and Integration environments. If you use this data in Staging or Production, make sure to clear out the information and products before going live.

For instructions, see Install optional sample data.

Optional: Pull production data

We recommend adding all of your products, catalogs, site content, and so on (not configurations) directly in Production. By adding this data in Production, you immediately update prices, coupons, inventory stock, strategize your sales and future offerings, and much more for your customers. This data does not include extension configurations. You will set those in your development branch on your local.

As you develop features, add extensions, and design themes, having real data to work with is helpful. At any time, you can create a database dump from Production and push that to your Staging environment, and possibly Integration environments as you like.