In this short blog post, I will show you how you can use shopware-cli to build your Shopware project and deploy it later with Deployer, Docker image whatever you want.

But first what is Shopware-CLI?

Shopware-CLI is a command line application written in Go. It’s not the same application as bin/console in your Project. It’s kinda a Swiss knife for the Shopware ecosystem. Likewise, it can do a lot of things like:

  • Build the assets of your extensions
  • Generate change log for the Shopware Store
  • Upload the extension to the store
  • Run multiple workers easily locally
  • MySQL dumps without MySQL binaries and compatible between MariaDB and MySQL
  • many things…
  • Build your Shopware project

Building your project

Before you deploy your project to the external service, you normally run some scripts in you favorite CI service. Things like:

  • Run composer install
  • Build Administration and Storefront
  • Warm up maybe the container

This config is always different for every project or used CI service. So with the new shopware-cli command we can build it with one single command and customize it when needed with YAML configuration. So it’s CI service neutral and can do more things than just some scripts.

Build your project with shopware-cli

First you will have to install shopware-cli in your CI. If you use GitHub Action, you can use our own action for this:

- name: Install shopware-cli
  uses: FriendsOfShopware/shopware-cli-action@v1
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

For any other CI service, we provide multi-arch (amd64/arm64) Docker images. You can find them on Docker Hub or GitHub.

After you installed shopware-cli, you can run the following command to build your project:

> shopware-cli project ci <path-to-root>

So the Command will build Shopware and run a lot of optimizations:

  • Run composer install with optimized class loader and classmap-authoritative (Composer cannot find dynamic generated classes anymore, safes performance)
  • Builds Administration and Storefront when required
    • Checks which extensions require what build
    • Runs npm install for all extensions
    • Commands like bin/console bundle:dump etc. are rewritten in Go and requires so less PHP execution (better as we don’t have our Database in our CI).
  • Deleting many unnecessary files to save space
    • Whole Administration source code after build
    • Many fonts from TCPDF (Shopware uses DomPDF, TCPDF is only used to merge PDF files)
    • All administration source code from all installed extensions (Requires at least Shopware
    • Deletes node_modules folders
  • Optimize snippets in Administration
    • Developers save their Administration snippets always to the same folder to their modules. With that style we get in the Administration a lot of snippet files. To clean this up and optimize the performance, we merge all snippets into one file.

Size difference:

Normal Shopware: 276 MB

Shopware with shopware-cli: 181 MB

The size matters for the deployment time and the disk space on the server. When Docker is used, the image size will be also much smaller.

I think this is just the beginning, and we can do a lot more in the future. The goal is it with the command to make your life deploying Shopware easy as possible and have one common way to do it regardless what your target platform is.


The command is configurable with a YAML file. The config looks like this:

# .shopware-project.yml
  # deletes all public source folders of all extensions, can be only used when /bundles is served from local and not external CDN
  remove_extension_assets: false
  # skips the bin/console asset:install part
  disable_asset_copy: false
  # delete additional paths after build
    - path

Checkout the Shopware project yaml configuration reference page for all possible configurations.


I hope you like the new command, and it helps you to build your project in the CI. You can check out also production-docker from FriendsOfShopware where we use that command to build docker images for production. If you have any questions or feedback, feel free to contact me in the Community Slack (#friendsofshopware channel) or open an issue on GitHub.