{"id":62579,"date":"2024-07-15T14:59:28","date_gmt":"2024-07-15T09:29:28","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=62579"},"modified":"2024-07-15T15:01:13","modified_gmt":"2024-07-15T09:31:13","slug":"ultimate-guide-to-deploying-code-on-adobe-commerce-cloud","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/ultimate-guide-to-deploying-code-on-adobe-commerce-cloud\/","title":{"rendered":"Ultimate Guide to Deploying Code on Adobe Commerce Cloud"},"content":{"rendered":"

Our previous blog<\/a><\/span> detailed the process of setting up our environment for code deployment. In this blog, we will focus on how to deploy code changes. To avoid straying from our main topic, we will not demonstrate the development of the module. Instead, we will use a premade custom module as an example.<\/p>\n

Local Development and Testing<\/h2>\n

As we mentioned, in our previous blog, you can create a directory of your own choice and install the Magento. Let\u2019s say we named the directory\u00a0 <\/span>ttn-local-env. <\/i><\/b>\u00a0The next steps would be,<\/span><\/p>\n

    \n
  1. To develop a new module. (We developed a simple module for demo purposes, which displays the text \u201cHello from TTN Team!!!\u201d)<\/span><\/li>\n
  2. Once you are ready with the code to deploy, build and deploy it on the local magento server using the following commands,<\/span><\/li>\n<\/ol>\n
    php bin\/magento setup:upgrade\r\nphp bin\/magento cache:flush<\/span><\/i><\/pre>\n
    You should be able to see the changes you developed.<\/span><\/p>\n
    \"Local
    Local Env<\/p><\/div>\n
    Sync the Cloud Dev environment<\/h2>\n
    If the changes on the local dev environment look good, we can bring the cloud dev server up to sync.<\/span> We have developed our code in <\/span>ttn-local-env<\/b> directory, to commit and push the changes\u00a0<\/span><\/p>\n
      \n
    1. We will copy over only the changed code files to the <\/span>dev<\/i><\/b> (under \/<\/span>var\/www\/html\/<cloud-folder><\/span><\/i>) directory.\u00a0<\/span><\/li>\n
    2. Commit and push the changes on the <\/span>dev<\/i><\/b> branch.\u00a0<\/span><\/li>\n
    3. Test and verify the same changes on the cloud dev environment too.<\/span><\/li>\n<\/ol>\n
      Progress the changes to higher environments<\/h2>\n
      Now that you have validated the changes and are ready for a higher environment. Let\u2019s go ahead and push the changes on the Stage.<\/p>\n
        \n
      1. To merge the dev changes, we will first checkout on the Stage branch, and take a pull of the dev branch.<\/li>\n
      2. Finally using the git push<\/em> command we will deploy the changes on the Stage environment.<\/li>\n<\/ol>\n
        Similarly, the same steps are to be followed for the Master environment and the Master branch. The only difference in this case would be that, instead of merging the dev branch to the master branch, you will merge the stage branch to the master. And use the same git push command to deploy the master branch.<\/p>\n
        After doing those changes, your changes will be live, and you can verify them on the master environment.<\/p>\n
        \"Master
        Master Env<\/p><\/div>\n
        With this, we conclude with our deployment and 2 part blog series where in the first part we covered how to set up Adobe Commerce on the Cloud. And, in the second part, we saw how we can deploy the code changes.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
        Our previous blog detailed the process of setting up our environment for code deployment. In this blog, we will focus on how to deploy code changes. To avoid straying from our main topic, we will not demonstrate the development of the module. Instead, we will use a premade custom module as an example. Local Development […]<\/p>\n","protected":false},"author":1383,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":19},"categories":[5868],"tags":[1522,5059,5116,1916],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62579"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1383"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=62579"}],"version-history":[{"count":6,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62579\/revisions"}],"predecessor-version":[{"id":63111,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62579\/revisions\/63111"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=62579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=62579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=62579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}