I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Issues related (if applicable)
None.
Screenshots or Videos
Not included.
Greptile Summary
This PR adds a complete Shopware 6 blueprint with a multi-stage init chain (bootstrap → init-permissions → init → runtime services), MySQL 8.4, Redis 7.4, a background worker, and a scheduler. All repo conventions are met: version 3.8, named volumes only, expose instead of ports, and the primary service is named shopware to match the blueprint folder.
The only finding is a minor inconsistency in the init, shopware, worker, and scheduler entrypoints, which use a bare $ for shell command substitutions ($(cat ...)) while bootstrap correctly uses $$ to escape the $ from Docker Compose's variable interpolation engine. In practice this works on current Docker Compose v2, but the $$ form is the guaranteed-safe approach.
Confidence Score: 5/5
Safe to merge — the only finding is a cosmetic $ vs $$ inconsistency that works correctly on all current Docker Compose v2 releases.
All remaining findings are P2 style suggestions. The blueprint is functional, tested by the author, follows all repo conventions, and prior review feedback on restart policies and failed-queue documentation has been fully addressed.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/782
**Author:** [@zrja](https://github.com/zrja)
**Created:** 4/9/2026
**Status:** ✅ Merged
**Merged:** 7/8/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `zrja/shopware-v1`
---
### 📝 Commits (6)
- [`ac5f9b9`](https://github.com/Dokploy/templates/commit/ac5f9b995a379e56d5ac3fc684ebc86fcaa91e3e) feat: add shopware blueprint
- [`3100430`](https://github.com/Dokploy/templates/commit/3100430dc56e8a17d91c561fa0cadae728284ce5) fix: address shopware review feedback
- [`d0821bd`](https://github.com/Dokploy/templates/commit/d0821bdb39cf8c2572f00d316b9793e475eb5408) fix: remove duplicate strapi entry
- [`fed39e3`](https://github.com/Dokploy/templates/commit/fed39e395e00f80b0253dc6f9ace384cad1ed119) fix: address remaining shopware review notes
- [`3a56077`](https://github.com/Dokploy/templates/commit/3a56077d39631dd56e673fc887f8e4214acbbd87) Merge remote-tracking branch 'origin/canary' into zrja/shopware-v1
- [`987fdf3`](https://github.com/Dokploy/templates/commit/987fdf3c099c95de6b2fdcc59aa5ce8a1dd6fdaf) fix: composer security audit blocked pinned shopware/core, bump to 6.7.12.1
### 📊 Changes
**4 files changed** (+453 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/shopware/docker-compose.yml` (+332 -0)
➕ `blueprints/shopware/logo.svg` (+24 -0)
➕ `blueprints/shopware/meta.json` (+19 -0)
➕ `blueprints/shopware/template.toml` (+78 -0)
</details>
### 📄 Description
## What is this PR about?
New PR of Shopware
This PR:
- adds a new `shopware` blueprint with `docker-compose.yml`, `template.toml`, and `logo.svg`
- adds the `shopware` entry to `meta.json`
- runs `node dedupe-and-sort-meta.js`
- addresses review feedback by pinning image tags and renaming the primary service to `shopware`
## Checklist
Before submitting this PR, please make sure that:
- [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [x] I have added tests that demonstrate that my correction works or that my new feature works.
## Issues related (if applicable)
None.
## Screenshots or Videos
Not included.
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a complete Shopware 6 blueprint with a multi-stage init chain (bootstrap → init-permissions → init → runtime services), MySQL 8.4, Redis 7.4, a background worker, and a scheduler. All repo conventions are met: version `3.8`, named volumes only, `expose` instead of `ports`, and the primary service is named `shopware` to match the blueprint folder.
The only finding is a minor inconsistency in the `init`, `shopware`, `worker`, and `scheduler` entrypoints, which use a bare `$` for shell command substitutions (`$(cat ...)`) while `bootstrap` correctly uses `$$` to escape the `$` from Docker Compose's variable interpolation engine. In practice this works on current Docker Compose v2, but the `$$` form is the guaranteed-safe approach.
<h3>Confidence Score: 5/5</h3>
- Safe to merge — the only finding is a cosmetic `$` vs `$$` inconsistency that works correctly on all current Docker Compose v2 releases.
- All remaining findings are P2 style suggestions. The blueprint is functional, tested by the author, follows all repo conventions, and prior review feedback on restart policies and failed-queue documentation has been fully addressed.
- No files require special attention.
<sub>Reviews (2): Last reviewed commit: ["fix: address remaining shopware review n..."](https://github.com/dokploy/templates/commit/fed39e395e00f80b0253dc6f9ace384cad1ed119) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27807934)</sub>
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/782
Author: @zrja
Created: 4/9/2026
Status: ✅ Merged
Merged: 7/8/2026
Merged by: @Siumauricio
Base:
canary← Head:zrja/shopware-v1📝 Commits (6)
ac5f9b9feat: add shopware blueprint3100430fix: address shopware review feedbackd0821bdfix: remove duplicate strapi entryfed39e3fix: address remaining shopware review notes3a56077Merge remote-tracking branch 'origin/canary' into zrja/shopware-v1987fdf3fix: composer security audit blocked pinned shopware/core, bump to 6.7.12.1📊 Changes
4 files changed (+453 additions, -0 deletions)
View changed files
➕
blueprints/shopware/docker-compose.yml(+332 -0)➕
blueprints/shopware/logo.svg(+24 -0)➕
blueprints/shopware/meta.json(+19 -0)➕
blueprints/shopware/template.toml(+78 -0)📄 Description
What is this PR about?
New PR of Shopware
This PR:
shopwareblueprint withdocker-compose.yml,template.toml, andlogo.svgshopwareentry tometa.jsonnode dedupe-and-sort-meta.jsshopwareChecklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
None.
Screenshots or Videos
Not included.
Greptile Summary
This PR adds a complete Shopware 6 blueprint with a multi-stage init chain (bootstrap → init-permissions → init → runtime services), MySQL 8.4, Redis 7.4, a background worker, and a scheduler. All repo conventions are met: version
3.8, named volumes only,exposeinstead ofports, and the primary service is namedshopwareto match the blueprint folder.The only finding is a minor inconsistency in the
init,shopware,worker, andschedulerentrypoints, which use a bare$for shell command substitutions ($(cat ...)) whilebootstrapcorrectly uses$$to escape the$from Docker Compose's variable interpolation engine. In practice this works on current Docker Compose v2, but the$$form is the guaranteed-safe approach.Confidence Score: 5/5
$vs$$inconsistency that works correctly on all current Docker Compose v2 releases.Reviews (2): Last reviewed commit: "fix: address remaining shopware review n..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.