Before we dive into the installation process for Adobe Commerce or Magento Open Source, it is crucial to ensure that your system meets the necessary technical requirements. I hope you decided to follow the installation process for Warden, as explained in Chapter 1.

You can find this chapter’s code in this book’s GitHub repository: https://github.com/PacktPublishing/Mastering-Adobe-Commerce-Frontend. This repository contains a VirtualBox image with everything already configured, as well as some scripts to help you out with the installation process.

The eCommerce framework Magento was created by Varien Inc. and launched on March 31, 2008. It was made available as a fully open source platform for all to use. Some significant companies, including eBay and PayPal, have been involved with Magento since then. It was offered in two versions:

• Community Edition: Fully open source version for everyone
• Enterprise Edition: A paid version of the Magento platform with extra features and some performance improvements that were not part of the open source version

Magento 1 was – and remains – an excellent platform. The development of a new version, simply called Magento 2, was ongoing for several years and was released on November 17, 2015. In my personal opinion, the platform was released too soon, and it took Magento over 2 years to produce something much more stable that could be used on production sites.

In 2018, Adobe acquired Magento. After Magento 2 was released and Adobe...

Is it not that easy to get the Adobe Commerce version for local development, especially if you are a freelancer and you are just staging your journey with Adobe Commerce/Magento frontend development. It is much easier if you work for a larger agency that does have multiple projects on this platform already and they can share a pair of composer keys with you.

Wait… a pair of what? This is where we need to introduce another tool that will be required to run Adobe Commerce/Magento Open Source on your local instance – Composer:

Figure 2.1 – Composer logo

Now, I don’t want to dive into too many details again, so let me explain this in a very simple way. If you know a little about npm for Node.js or Bundler for Ruby, Composer is the same tool for PHP – it is a package manager. Some people say that Composer is the best package manager. Its role is to manage code dependencies...

We will install the platform from scratch using Warden, so let’s get started! Open your terminal application (we will be using it a lot more from now on) and follow these steps:

Working on Windows WSL

For this book, all coding tasks and operations will be done on a Windows machine to cover all based related to file sync between your local drive and the WSL 2 drive. The next few steps have been done on a Windows machine.

1. Make sure your Warden environment is working by typing the following:

   warden svc up

   You should see the following output:

Figure 2.10 – Checking whether Warden is running

2. Create a folder for your project. For our purposes, we will name it packt1 by using the mkdir command:

   mkdir packt1

   You can also create a folder by navigating to a proper folder, but you will still have to access it via CLI | terminal.

3. Enter the folder you created using cd:

   cd packt1

...

This is the moment when things might get a little complicated as we will be working with the CLI a lot and we’ll be running many commands in the next few chapters. To get started, follow these steps:

1. In your terminal application/CLI, log into your application container by typing the following:

   warden shell

   This will log you into the Docker container that is running the PHP code:

Figure 2.14 – Logging into the Docker container

Here’s the bad news: Adobe Commerce has no web installer available, so you have to install everything using the CLI. To do this, run all those commands in the Docker container you’ve just logged into.

2. Next, configure the Magento keys:

   composer global config http-basic.repo.magento.com <username> <password>

   Here, username is a public key and password is a private key.

   When you are taking over a project, it is very important to check magento...

In this chapter, you learned about some of the history behind AC and Magento. You created the required accounts and learned about the importance of Composer keys. You also learned how to get the platform running in a Dockerized environment from scratch and dipped your toes into CLI commands.

In the next chapter, I’ll guide you through the basic concepts of AC theming and I’ll share much more knowledge about the platform itself – knowledge that, in my opinion, is a must-know for any Adobe Connect/Magento Open Source developer, as well as eCommerce managers.

We will create a new theme and understand the concepts and the role of the Adobe Connect caching system before I describe more areas of the platform itself so that will never run into any issues during development.

You will also learn the basics of the fallback system and how to compile fewer files to produce the CSS files used by Adobe Connect. Simply put, things will finally be more development...

To solidify your understanding of this chapter, please try out the following practical exercises:

1. Create a new project called packt2 from scratch and install Adobe Commerce/Magento Open Source with sample data.
2. Move one of your existing Adobe Commerce/Magento Open Source projects to Warden.

   Note that this might require at least three key elements:

   1. Repository access.
   2. Media files package.
   3. Latest database dump.