Repository navigation
docs: document Composer-in-container and PHP memory limit for CLI Docker - #2436
Conversation
Clarify that Docker projects should run Composer inside the web container, that the TUI runtime memory check does not cover host PHP, and that Shopware requires memory_limit ≥ 512M when running PHP on the host. Related to shopware/shopware-cli#1343.
Developer Docs healthcheckStatus: Completed with |
📊 Documentation Impact Analyzer
Reasons
|
There was a problem hiding this comment.
Pull request overview
Documents the Docker-first workflow for Shopware CLI projects by clarifying that Composer/PHP/npm commands should be executed inside the web container, and by surfacing the memory_limit ≥ 512M requirement and common host-side OOM troubleshooting across key entry points in the docs.
Changes:
- Adds cross-links and callouts to run Composer/PHP/npm inside
docker compose exec web …for Docker-based projects. - Clarifies that the DevTUI “Setup health → Runtime → Memory limit” reflects container PHP, not host PHP used by a local Composer binary.
- Adds a troubleshooting note for the common host-side memory exhaustion error (
Allowed memory size of 134217728 bytes exhausted).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| products/tools/cli/project-commands/helper-commands.md | Adds a Docker-specific note linking to the new “Running Composer, PHP, and npm” section and the memory limit requirement. |
| products/tools/cli/project-commands/dev-environment.md | Adds an additional “Further reading” entry pointing to the new container-tools guidance. |
| products/tools/cli/index.md | Updates requirements guidance to point to hosting “recommended stack” (incl. memory limit) and links Docker users to the new section. |
| guides/installation/project-overview.md | Adds docker compose exec web … as a core day-to-day command and explains why host Composer/PHP differs from container runtime. |
| guides/installation/index.md | Adds a tip admonition emphasizing container-executed Composer/PHP tools for Docker installs and links to the new section. |
| guides/development/start-developing.md | Adds a dedicated section on running Composer inside the container and updates private Composer registry auth guidance. |
| guides/development/dev-environment.md | Expands DevTUI runtime/memory explanation, adds a new “Running Composer, PHP, and npm” section, and adds OOM troubleshooting. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
📢 Developer Announcement RecommendationRecommendation: ❌ No Announcement Recommended No developer announcement signals were detected.
|
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Su (@sushmangupta) yes it was right applied it |
Su (sushmangupta)
left a comment
Su (sushmangupta)
left a comment
There was a problem hiding this comment.
Thanks for the PR Soner (@shyim) :)
Summary
webcontainer (docker compose exec web …), not on the host.memory_limit ≥ 512Mon the CLI/dev documentation path (installation, start-developing, CLI index, helper commands).Allowed memory size of 134217728 bytes exhausted).Addresses the documentation gap discussed in shopware/shopware-cli#1343.
Test plan
#running-composer-php-and-npmworks in the developer portal preview