Skip to content



The source code of your project will reside in a git-based VCS repository. You can start with a plain project. However, we suggest starting with a new Composer create-project. You will learn more about the setup template in the Setup Template section.


This guide explains the repository setup using GitHub. You can also integrate Bitbucket or GitLab-based version control environments with Shopware PaaS. Refer to Source Integrations for more information.

Create a Shopware project

Firstly, create a new project with composer create-project shopware/platform:dev-flex <folder-name> using the Symphony Flex template.

This will create a brand new Shopware 6 project in the given folder. Now, change it into the newly created project and require the PaaS configuration with composer req paas.

Secondly, create a new Git repository and push it to your favorite Git hosting service.

Add PaaS remote

Lastly, add a second remote, which allows us to push code towards the PaaS environment and trigger a deployment.

We first need the project ID, so we display all projects using

$ shopware projects

Your projects are:
| ID            | Title     | Region           | Organization |
| 7xasjkyld189e | paas-env  | <region-domain>  | shopware     |

Get a project by running: platform get [id]
List a projects environments by running: platform environments -p [id]

To add the project remote to your local repository, just run

shopware project:set-remote 7xasjkyld189e # Replace with your project ID


Now your repository is configured - you should have three remotes

$ git remote -v

origin<project-repository>.git (fetch)
origin<project-repository>.git (push)
platform	<paas-url>.git (fetch)
platform	<paas-url>.git (push)
originProject CodeThis remote contains all your project specific source code
platformPaaS EnvironmentChanges pushed to this remote will be synced with your PaaS environment

Migrating from old template to the new template

If you have already used the Shopware PaaS old template, please follow the guide to migrate it to the new structure.

Following tasks has to be done additionally to the flex migration:

  • The root has been moved to .platform/applications.yaml
  • The following services has been renamed:
    • queuerabbit to rabbitmq
    • searchelastic to opensearch

As the services are renamed, a completely new service will be created. Here are three possible options available: