For example, if you use the simple command with no options, the CLI prompts you to select which mount or mounts to upload or download. Both commands use the rsync utility, but the CLI commands provide options and prompts tailored to the Adobe Commerce on cloud infrastructure environment. You can use the mount:upload and mount:download CLI commands to migrate files between the local and remote environment. ![]() And Adobe recommends using the rsync method when moving files from a remote source to a different remote location. Both methods use the rsync utility, but Adobe recommends using the magento-cloud CLI for moving files between the local and remote environment. There are two methods for migrating files from a source mount location, such as your local environment, to a destination mount location. Merge the Staging environment to Production to deploy: magento-cloud environment:merge Merge the integration environment to Staging to deploy: magento-cloud environment:merge Ĭheck out, synchronize, and create a snapshot of your local Production environment. Synchronize your local Staging environment with the remote environment: magento-cloud environment:synchronize Step 2: Merge changes to Staging and deployĬheck out the Staging environment: magento-cloud environment:checkout git add -A & git commit -m "Commit message" & git push origin Update code in your local branch as needed.Īdd, commit, and push changes to the environment. Synchronize your local integration environment with the remote environment: magento-cloud environment:synchronize Ĭreate a snapshot of the environment as a backup: magento-cloud snapshot: create -e Step 1: Deploy and test the integration environmentĪfter logging into the project, check out the integration environment: magento-cloud environment:checkout You need SSH and Git access to your project. The Cloud CLI provides commands to deploy code. When Staging is ready, select the Merge option to deploy to Production ( master). When Staging is ready, select the Merge option to deploy to Production.įor Starter, deploy the development branch to Staging: Select the Merge option to deploy to Staging.Ĭomplete all testing in the Staging environment. ![]() ![]() The Project Web Interface provides features to create, manage, and deploy code in Integration, Staging, and Production environments for Starter and Pro plans.įor Pro projects, deploy the Integration branch to Staging: Deploy code with the Project Web Interface You can fully push, merge, and deploy through the Project Web Interface or Cloud CLI commands through a terminal application. The Staging environment provides a near-production environment that includes a database, web server, and all services including Fastly and New Relic. Although the integration environment can have many branches, Staging and Production have only one branch for each environment.įor detailed information of the process, see Pro Develop and Deploy Workflow. When you create your project, code is ready to branch, develop, and push for building and deploying your site. ![]() Pro comes with a large integration environment with two active branches, a global master branch, Staging, and Production branches. Then you have two of your four active environments ready: master for Production and staging for Staging.įor detailed information of the process, see Starter Develop and Deploy Workflow. Starter deployment flowĪdobe recommends creating a staging branch from the master branch to best support your Starter plan development and deployment. Adobe recommends creating a snapshot of the environment before deployments.Īlso, you can enable Track deployments with New Relic to monitor deployment events and help you analyze performance between deployments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |