Shopware on myl3z.me

What ddev Is

Mon, 01 Jan 0001 00:00:00 +0000

What ddev Is#

ddev is an open-source tool that creates and manages local development environments in Docker containers. Instead of installing and maintaining PHP, MySQL, Node and nginx on your own machine, you describe in a single file what a project needs — and ddev turns that into a running environment.

In practice: ddev start inside a project directory, and a few seconds later the shop is served over HTTPS.

Installing ddev

Mon, 01 Jan 0001 00:00:00 +0000

Installing ddev#

Once per machine. After that, every further project is a matter of minutes.

Exactly two things are needed: Docker and ddev. Everything else — PHP, Composer, Node, MySQL — ddev ships in containers.

Step 1: Docker#

ddev needs a Docker provider. Which one barely matters, as long as it runs.

Linux

Docker CE straight from the distribution, the quickest option:

# Arch
sudo pacman -S docker docker-buildx
sudo systemctl enable --now docker
sudo usermod -aG docker "$USER"

# Debian / Ubuntu
curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker "$USER"

After usermod, log out and back in once, otherwise the permissions on the Docker socket are missing.

Setting Up Shopware 6

Mon, 01 Jan 0001 00:00:00 +0000

Setting Up Shopware 6#

From an empty directory to a configured shop. The example is tydace, a freshly installed Shopware 6.7 shop.

Time needed: just under ten minutes, most of it waiting for Composer.

The Skeleton#

1. Create the Project#

mkdir tydace && cd tydace
ddev config --project-type=shopware6 --docroot=public

ddev config writes .ddev/config.yaml. The project type shopware6 sets the matching nginx configuration and the environment variables Shopware expects; --docroot=public tells ddev where index.php lives.

Working With It Daily

Mon, 01 Jan 0001 00:00:00 +0000

Working With It Daily#

The shop runs. What matters now are the ten commands you genuinely use every day — and a few habits that save a lot of time.

The Ground Rule#

Anything concerning the shop runs inside the container. So ddev composer instead of composer, ddev console instead of bin/console, ddev npm instead of npm. The reason is always the same: inside the container the project’s PHP and Node versions apply, on the machine those of the machine.