{"id":60600,"date":"2024-03-11T09:49:48","date_gmt":"2024-03-11T04:19:48","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=60600"},"modified":"2024-06-10T15:33:11","modified_gmt":"2024-06-10T10:03:11","slug":"setup-adobe-commerce-on-cloud","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/setup-adobe-commerce-on-cloud\/","title":{"rendered":"Setup Adobe Commerce on Cloud"},"content":{"rendered":"

Adobe Commerce is an enterprise-level eCommerce platform that is flexible and scalable. It lets businesses create personalized B2B and B2C online stores. But before businesses can set up their online store on Adobe Commerce, it has to be set up first!\u00a0<\/span><\/p>\n

In this two-part blog series, we\u2019ll delve into the setup of Adobe Commerce on Cloud infrastructure. Additionally, we’ll also explore the development process on a high level. This very blog will exclusively cover the setup part, and the development process will be covered in the next part of the same series, hence stay tuned.<\/span><\/p>\n

Prerequisites<\/strong><\/h2>\n
    \n
  1. To set up Adobe Commerce, the essential requirement is configuring the <\/span>SSH keys<\/b>. For that, create an SSH key and configure it in the <\/span>Account Settings<\/i><\/b> tab in your Magento Account<\/a><\/span>.\u00a0<\/span><\/li>\n
  2. The next important step is to clone the project; you can find the clone command below, or you can refer screenshot<\/em>,<\/span><\/span><\/li>\n<\/ol>\n

    git clone –branch master <project_id>@<git_repo_name>.git dev<\/i><\/strong><\/span><\/span><\/p>\n

    \"GIT

    GIT Clone command<\/p><\/div>\n

    Setup Master Environment<\/strong><\/h2>\n

    When you access your project from the <\/span>Projects<\/i><\/b> tab, the default environment is <\/span>Master<\/b>. Installing Magento on this environment involves SSHing into the Master. You can install it from this source if you don’t have Cloud CLI<\/span>.<\/span><\/p>\n

    To SSH into the Master environment, copy the command from the Project console, which should look like this,<\/span><\/p>\n

    magento-cloud ssh --project <project-code>--environment master \u00a0 --app mymagento<\/em><\/pre>\n
     <\/p>\n
    \"Cloud
    Cloud SSH Command<\/p><\/div>\n
    Now that we’ve accessed the Master environment, it’s time to install Magento. We’ve previously covered Magento installation in one of our earlier <\/span>blog posts<\/span><\/a>, where we had also set up the Venia store. Here, I’ll share the command; feel free to customize it with your details and execute it.<\/span><\/p>\n
    NOTE: <\/b><\/span>Make sure you update the <\/span>base-url<\/i><\/b> value with the <\/span>HTTP URL<\/i><\/b> of your Master env, which can be found here (see screenshot)<\/em>,<\/span><\/p>\n
    \"Environment
    Environment URLs<\/p><\/div>\n
    php bin\/magento setup:install \\\r\n<\/span><\/i>\u00a0 \u00a0--admin-firstname=admin \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--admin-lastname=admin \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--admin-email=admin@abc.com \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--admin-user=admin \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--admin-password=12345 \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--base-url=<\/span><\/i><http URL><\/i><\/b> \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--db-host=database.internal \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--db-name=dbName \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--db-user=ttn \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--currency=USD \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--timezone=America\/Chicago \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--language=en_US \\\r\n<\/span><\/i>\u00a0\u00a0\u00a0--use-rewrites=1<\/span><\/i><\/pre>\n
    Verify the installation by visiting the website.<\/span><\/p>\n
    Creating Lower environments<\/strong><\/h2>\n
    We’ll establish a <\/span>staging environment for conducting production-level testing and a Development<\/b><\/span>\u00a0environment for development purposes. The Staging environment will be generated based on the Master environment.<\/span> Navigate to the <\/span>dev<\/i><\/b> directory inside the <\/span>\/var\/www<\/span><\/i> directory and checkout a new staging branch,<\/span><\/p>\n
    git checkout -b Staging<\/i><\/strong><\/pre>\n
    Push the same change to the staging branch,<\/span><\/p>\n
    git push origin Staging<\/i><\/strong><\/pre>\n
    The environment is not active yet. To activate it, run the following command,<\/span><\/p>\n
    magento-cloud environment:activate Staging<\/strong><\/em><\/pre>\n
    You can check its activation status from the console,<\/span><\/p>\n
    \"Environment
    Environment Info<\/p><\/div>\n
    One good thing is, that we do not have to install Magento again in this environment. Similarly, <\/span>follow the steps above to create a Dev environment.<\/span><\/p>\n
    Setup Local Magento<\/strong><\/h2>\n
    For our code development, we would need Magento on our local server and in a separate directory; you can name the folder anything. Some dependencies can be used to install Magento on local servers, such as Apache, MySQL, and PHP. We have already covered in detail how to install those in our <\/span>previous blog<\/span><\/a>; you\u00a0can refer to that.<\/span><\/p>\n
    To summarize, this blog covered the setup of Adobe Commerce on Cloud, addressing SSH key configuration, Magento installation on the Master environment, and the establishment of lower environments for staging and development. Expect more insights in the upcoming part of the series. <\/span><\/p>\n
    Stay tuned for the next part of this blog, in which we will delve into the development processes!<\/span><\/p>\n
    <\/div>","protected":false},"excerpt":{"rendered":"
    Adobe Commerce is an enterprise-level eCommerce platform that is flexible and scalable. It lets businesses create personalized B2B and B2C online stores. But before businesses can set up their online store on Adobe Commerce, it has to be set up first!\u00a0 In this two-part blog series, we\u2019ll delve into the setup of Adobe Commerce on […]<\/p>\n","protected":false},"author":1383,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":25},"categories":[5868,4308],"tags":[5061,5059,4847,2838,911],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60600"}],"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=60600"}],"version-history":[{"count":2,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60600\/revisions"}],"predecessor-version":[{"id":60755,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60600\/revisions\/60755"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=60600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=60600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=60600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}