fix: update TYPO3_PATH directory for build process

[konradmichalik]

Summary by CodeRabbit

• Bug Fixes
  • Improved detection of installed TYPO3 versions by updating the lookup location, ensuring commands run reliably in local environments.

[coderabbitai]

Walkthrough

The script at .ddev/commands/web/all was updated to change the TYPO3_PATH lookup base directory from /var/www/html/.test/${version} to /var/www/html/.Build/${version}. The rest of the logic remains unchanged, including iterating over versions, checking directory existence, constructing commands, changing directories, and executing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1780904 and f5ff560.

📒 Files selected for processing (1)

• .ddev/commands/web/all (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

.ddev/commands/web/all (1)

.ddev/.typo3-setup/scripts/utils.sh (8)

• post_setup (103-118)
• setup_environment (146-157)
• post_setup_11 (243-252)
• setup_typo3 (201-213)
• update_typo3 (217-220)
• pre_setup (90-97)
• post_setup_12 (257-265)
• post_setup_13 (270-276)

🔇 Additional comments (2)

.ddev/commands/web/all (2)

14-14: Path update aligns with project conventions (.Build) — good change

This switch to /var/www/html/.Build/${version} matches the BASE_PATH used across .ddev/.typo3-setup/scripts/utils.sh and keeps the tooling consistent.

---

14-14: No leftover .test references found
A repository-wide search returned zero matches for /.test/, and all .Build/ paths (e.g., in composer.json) are consistently applied.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-ddev-all-command

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.