Here’s our latest TYPO3-with-DDEV news wrap-up, following up April’s roundup. What you need to know:
Please, Ask Us Questions, Explain Frictions You Find in DDEV!
I think you’ve all seen the change AI has brought in interaction with software. It’s mighty effective in answering questions, often correctly, and it does a great job with DDEV and TYPO3 issues, because both are so widely and openly documented.
But remember what is happening here! We need to hear from you to understand your experience. We love to hear from you! All this is not just about you getting an answer to move forward, it’s about maintainers getting the feedback they need about frictions, missing features, and inadequate documentation. When you have a question or problem with DDEV, it’s OK to get an answer from AI, but please ask us and help us understand it as well. Join us in Discord or the issue queue. We delight in interacting with you.
DDEV Share Is Even Better, With Screencast
Sharing Your TYPO3 Project with ddev share (Video) shows how you can share your local project for review or collaboration or discussion with anybody on the internet.
Git Worktree for Working on Multiple Features (or Multiple AI Agents)
Git Worktree with TYPO3 (video) demonstrates how you can run multiple DDEV projects from the same Git repository at the same time, with separate code changes, databases and URLs. Even when projects hardcode a full URL in config/sites/*/config.yaml’s base, a simple set of post-start hooks can fix that. The fix there is elegant once you see it: a pre-share hook strips base down to just its path (dropping the scheme and hostname entirely), so it matches whatever hostname the request actually arrives on, and a post-share hook restores the original value afterward.
TYPO3 on coder.ddev.com
coder.ddev.com runs a full DDEV environment in the cloud, no local Docker required. TYPO3 Projects on Coder.ddev.com walks through using it with the freeform template.
Unlike ddev share’s temporary tunnel, coder.ddev.com gives each workspace a stable *.coder.ddev.com subdomain via Traefik host-header routing, which maps that stable external hostname to the right project every time.
Access to coder.ddev.com is a perk for organizations that sponsor DDEV at $100+/month (b13 is one partner in the TYPO3 space), but individuals can also request access directly.
DDEV v1.25.3: Faster, and Docker/Podman Rootless Is Stable
DDEV v1.25.3 is out, with ddev start about 28% faster than v1.25.2, and a similar improvement to ddev stop, ddev restart, and ddev poweroff.
Podman and Docker Rootless, introduced as experimental in v1.25.0, are now stable. Other changes include a built-in Docker Compose SDK (no more separate docker-compose binary to manage), MariaDB 12.3 LTS support, and several Node.js fixes.
New Diagnostic Utilities
A few new ddev utility commands help track down environment problems:
ddev utility port-diagnose checks whether another process is already occupying a port DDEV needs (HTTP, HTTPS, Mailpit, XHGui), including separately on WSL2’s Linux and Windows sides.
ddev utility tls-diagnose checks mkcert installation, OS trust store setup, and live HTTPS connectivity — useful when a browser doesn’t trust your DDEV project’s certificate.
ddev utility check-custom-config lists custom configuration files in your project, flagging ones that don’t look like they came from a recognized add-on, so you know what’s overriding DDEV’s defaults.
ddev utility addon-update-checker, for anyone maintaining a DDEV add-on (like the TYPO3 ones below), checks that your add-on’s scripts and tooling are current with DDEV’s add-on template.
