[PR #781] [CLOSED] feat: add Shopware blueprint #2092

New Issue

GiteaMirror · 2026-04-20T11:06:04-05:00

GiteaMirror commented

2026-04-20 11:06:04 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/781
Author: @zrja
Created: 4/9/2026
Status: ❌ Closed

Base: canary ← Head: zrja/shopware-integration

📝 Commits (2)

5ec1e73 fix: remove duplicate strapi metadata
dfb400a feat: add shopware blueprint

📊 Changes

4 files changed (+448 additions, -18 deletions)

View changed files

➕ blueprints/shopware/docker-compose.yml (+327 -0)
➕ blueprints/shopware/logo.svg (+24 -0)
➕ blueprints/shopware/template.toml (+78 -0)
📝 meta.json (+19 -18)

📄 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
removes the duplicate strapi entry from meta.json
runs node dedupe-and-sort-meta.js

Checklist

Before submitting this PR, please make sure that:

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
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.

None.

Screenshots or Videos

Not included.

Greptile Summary

This PR adds a new Shopware 6 blueprint with a multi-service Docker Compose stack (MySQL, Redis, bootstrap, init, worker, scheduler, and web), along with a template.toml, logo.svg, and a meta.json entry. It also removes a duplicate strapi entry from meta.json. The implementation is well-structured with proper use of YAML anchors, healthchecks, named volumes, and secret generation helpers.

Confidence Score: 5/5

Safe to merge; both findings are P2 style/hardening suggestions that don't block functionality.

All remaining findings are P2: the main service naming convention (AGENTS.md guidance) and the mutable image tags (security hardening). Neither causes a runtime failure, data loss, or auth bypass. The core blueprint logic, secret generation, healthchecks, and meta.json structure are all correct.

blueprints/shopware/docker-compose.yml — service naming and image tag pinning.

Vulnerabilities

shopware/shopware-cli:latest-php-8.4 and shopware/docker-base:8.4-nginx are floating/mutable image tags; pinning to a digest or exact release tag would reduce supply chain risk.
No secrets are hardcoded; all sensitive values use Dokploy's ${hash:...} and ${password:...} helpers.
No ports exposed on the host; expose is used correctly for internal routing.

_{Reviews (1): Last reviewed commit: "feat: add shopware blueprint" | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

Context used:

Context used - AGENTS.md (source)

_{🔄 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/781 **Author:** [@zrja](https://github.com/zrja) **Created:** 4/9/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `zrja/shopware-integration` --- ### 📝 Commits (2) - [`5ec1e73`](https://github.com/Dokploy/templates/commit/5ec1e7368c1f3025c4f1a08e3cd74adbd7669183) fix: remove duplicate strapi metadata - [`dfb400a`](https://github.com/Dokploy/templates/commit/dfb400aced64d1bc912355014f776723a941f2bc) feat: add shopware blueprint ### 📊 Changes **4 files changed** (+448 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/shopware/docker-compose.yml` (+327 -0) ➕ `blueprints/shopware/logo.svg` (+24 -0) ➕ `blueprints/shopware/template.toml` (+78 -0) 📝 `meta.json` (+19 -18) </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` - removes the duplicate `strapi` entry from `meta.json` - runs `node dedupe-and-sort-meta.js` ## 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 - [ ] 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.  <h3>Greptile Summary</h3> This PR adds a new Shopware 6 blueprint with a multi-service Docker Compose stack (MySQL, Redis, bootstrap, init, worker, scheduler, and web), along with a `template.toml`, `logo.svg`, and a `meta.json` entry. It also removes a duplicate `strapi` entry from `meta.json`. The implementation is well-structured with proper use of YAML anchors, healthchecks, named volumes, and secret generation helpers. <h3>Confidence Score: 5/5</h3> Safe to merge; both findings are P2 style/hardening suggestions that don't block functionality. All remaining findings are P2: the main service naming convention (AGENTS.md guidance) and the mutable image tags (security hardening). Neither causes a runtime failure, data loss, or auth bypass. The core blueprint logic, secret generation, healthchecks, and meta.json structure are all correct. blueprints/shopware/docker-compose.yml — service naming and image tag pinning. <details open><summary><h3>Vulnerabilities</h3></summary> - `shopware/shopware-cli:latest-php-8.4` and `shopware/docker-base:8.4-nginx` are floating/mutable image tags; pinning to a digest or exact release tag would reduce supply chain risk. - No secrets are hardcoded; all sensitive values use Dokploy's `${hash:...}` and `${password:...}` helpers. - No `ports` exposed on the host; `expose` is used correctly for internal routing. </details> <sub>Reviews (1): Last reviewed commit: ["feat: add shopware blueprint"](https://github.com/dokploy/templates/commit/dfb400aced64d1bc912355014f776723a941f2bc) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=27805884)</sub> > Greptile also left **2 inline comments** on this PR. <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 11:06:04 -05:00

GiteaMirror closed this issue

2026-04-20 11:06:05 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#2092