Skip to content

Versioning and Dependencies

Versioning and Dependencies


This setup is no longer the recomended way to manage a Shopware installation. Please refer to our Flex-guide on how to migrate to a symfony flex based setup.


Shopware 6 production template

The Shopware 6 production template enables you to build, package and deploy Shopware 6 to production shops. This template is also used to build the official packages distributed by shopware.

shopware/production @ GitHub

The template is optimized for production usage and contains basic development tooling. It is intended as a basis for project customizations, which are usually done by agencies.

Branches and stability

In each commit, a composer.lock is contained to ensure that the version being deployed is the version that was tested in our CI. We currently provide the following branches:

  • 6.3: stable minor and patch releases (v6.3.0.0-rc2, v6.3.0.1, v6.3.1.0, v6.1.*, but not v6.4.0.0)
  • trunk: stable major, minor, and patch releases (v6.3.0.0, v6.3.1.0, v6.4.0.0, v6.5.0.0...)

The 6.3 branch contains all the 6.3 releases. It is stable now and only gets non-breaking changes. (security issues are an exception).

The trunk branch contains the newest stable release, including major releases. That may result in plugins being incompatible, so be careful.

Starting with, we use a slightly modified version of SemVer. The pattern looks like this: 6.MAJOR.MINOR.PATCH. Examples:

  • - Major=3, Minor=2, Patch=5
  • - Major=4, Minor=1, Patch=0

See also:

Shopware 6 versioning strategy | Shopware


To get an overview of the requirements, refer to the following:


NPM and Node are only required during the build process and for development. If you don't have javascript customizations, it is not required at all because the Storefront and Admin are pre-build.

If you are using a separate build server, consider having NPM and Node as build-only requirements. Your operating application server doesn't require any of these to run Shopware 6.

Setup and install

To set up the environment and install it with a basic setup, run the following commands:

# clone newest 6.4 patch version from github 
git clone --branch=6.4 shopware
cd shopware

# install shopware and dependencies according to the composer.lock 
composer install

# setup the environment
bin/console system:setup
# or create .env yourself, if you need more control
# create jwt secret: bin/console system:generate-jwt-secret
# create app secret: APP_SECRET=$(bin/console system:generate-app-secret)
# create .env

# create database with a basic setup (admin user and Storefront sales channel)
bin/console system:install --create-database --basic-setup

# or use the interactive installer in the browser: /recovery/install/index.php


To update Shopware 6, just run this:

# pull newest changes from origin
git pull origin

# the (pre|post)-(install|update)-cmd will execute all steps automatically
composer install


This project is called production template because it can be used to create project specific configurations. The template provides a basic setup that is equivalent to the official distribution. If you need customization, the workflow could look like this:

  • Fork template
  • Make customization
  • Add dependencies
  • Add project specific plugins
  • Update var/plugins.json (bin/console bundle:dump, paths need to be relative to the project root)
  • Build Administration or Storefront
  • Update composer.json and composer.lock
  • Commit changes


Command overview

The following commands and scripts are available:


bin/console system:setupConfigure and create .env and optionally create jwt secret
bin/console system:generate-jwt-secretGenerates a new jwt secret
bin/console system:generate-app-secretOutputs a new app secret. This does not update your .env!
bin/console system:installSetup database and optional install some basic data
bin/console system:update:prepareRun update preparations before the update. Do not update if this fails
bin/console system:update:finishExecutes the migrations and finishes the update
bin/console theme:changeAssign theme to a sales channel



Bash is required for the shell scripts.

bin/console theme:compileCompile all assigned themes
bin/build.shComplete build including composer install
bin/build-js.shBuild Administration and Storefront, including all plugins in var/plugins.json.
bin/build-administration.shJust build the Administration.
bin/build-storefront.shJust build the Storefront. You need to have built the Administration once.


Run bin/ once to install the npm dependencies.


Bash is required for the shell scripts.

bin/console theme:refreshReload theme.json of active themes
bin/watch-administration.shWatcher for Administration changes, recompile and reload page if required
bin/watch-storefront.shWatcher for Storefront changes, recompile and reload page if required


See the in the config folder of the production template.

Template overview

This directory tree should give an overview of the template structure.

├── bin/                  # binaries to setup, build and run Symfony console commands 
├── composer.json         # defines dependencies and setups autoloading
├── composer.lock         # pins all dependencies to allow for reproducible installs
├── config                # contains application configuration
│   ├── bundles.php       # defines static Symfony bundles - use plugins for dynamic bundles
│   ├── etc/              # contains the configuration of the docker image
│   ├── jwt/              # secrets for generating jwt tokens - DO NOT COMMIT these secrets
│   ├── packages/         # configure packages - see: config/
│   ├── secrets/          # symfony secrets store - DO NOT COMMIT these secrets
│   ├── services/         # contains some default overrides
│   ├── services.xml      # just imports the default overrides - this file should not change
│   └── services_test.xml # just imports the default overrides for tests
├── custom                # contains custom files
│   ├── plugins           # store plugins
│   ├── static-plugins    # static project specific plugins
├── docker-compose.yml    # example docker-compose
├── Dockerfile            # minimal docker image
├── phpunit.xml.dist      # phpunit config
├── public                # should be the web root
│   ├── index.php         # main entry point for the web application
├──             # this file
├── src
│   ├── Command/*
│   ├── Kernel.php        # our kernel extension
│   └── TestBootstrap.php # required to run unit tests
└── var
    ├── log/              # log dir
    |── cache/            # cache directory for Symfony
    └── plugins.json      # javascript build configuration

Managing Dependencies


You only need to require the things you want. If you only want to run shopware 6 in headless mode, your composer.json could look like this:

    "name": "acme/shopware-production",
    "type": "project",
    "license": "MIT",
    "config": {
        "optimize-autoloader": true
    "prefer-stable": true,
    "minimum-stability": "stable",
    "autoload": {
        "psr-4": {
            "Shopware\\Production\\": "src/"
    "require": {
        "php": "~7.4.3",
        "shopware/core": "~v6.4.0"

Require project plugins

If you have project specific plugins, place them under custom/static-plugins/{YourPlugin} and require them in your composer.json.


The plugins needs a (stable) version to work with the default stability stable.

composer require "exampleorg/myplugin"

External plugins in private repositories can also be required by adding the repository to your composer.json. To learn more about the usage of private repositories, see here:

Using private repositories @

Update Shopware packages

Run the following command to update all shopware dependencies:

composer update "shopware/*"



The DOCKERFILE and docker-compose.yml service definitions should work but are still experimental.

Storage and caches

The following directories should be shared by all app servers:

├── config
│   ├── jwt # ro - should be written on first deployment
│   ├── secrets # rw shared - see, if you want to use it: 
├── public
│   ├── bundles # rw shared - Written by `assets:install` / `theme:compile`, can also be initiated by the Administration
│   ├── media # rw shared
│   ├── theme # rw shared - generated themes by `theme:compile/change`
│   └── thumbnail # rw shared - media thumbnails
│   └── sitemap # rw shared - generated sitemaps
├── var
│   ├── cache # rw local - contains the containers, which contains additional cache directories (twig, translations, etc)
│   ├── log # a - append only, can be change in the monlog config

ro - Readonly after deployment
rw shared - read and write access, it should be shared across the app servers
rw local - locale read and write access

Some of these directories, like public, can also be changed to a different Flysystem to host the files on S3.