A Claude Code skill for automating DDEV environment setup in TYPO3 extension projects
This skill helps TYPO3 extension developers quickly set up a complete DDEV development environment with multiple TYPO3 versions. Instead of manually configuring DDEV, this skill automates the entire process - from detecting your extension metadata to generating all configuration files and installing TYPO3.
- ✅ Detects TYPO3 extension projects automatically
- ✅ Extracts extension metadata (key, package name, namespace)
- ✅ Generates complete DDEV configuration
- ✅ Creates multi-version TYPO3 testing environment (11.5, 12.4, 13.4 LTS)
- ✅ Provides backend and frontend access with preconfigured credentials
- ✅ Includes custom DDEV commands for easy TYPO3 installation
- TYPO3 extension developers
- Teams working on TYPO3 extensions
- Developers needing to test extensions across multiple TYPO3 versions
- Anyone wanting a quick, reproducible TYPO3 development environment
Before using this skill, ensure you have:
- DDEV installed
- Docker running
- A TYPO3 extension project (with
ext_emconf.phporcomposer.json) - Claude Code installed
# Clone this repository into your Claude Code skills directory
cd ~/.claude/skills/ # or your custom skills directory
git clone https://github.com/netresearch/typo3-ddev-skill.git
# The skill is now available in Claude Code- Download this repository
- Copy the
skill.mdfile to your project or reference it when needed - Use the templates manually by copying from the
templates/directory
Once installed, simply invoke the skill in your TYPO3 extension project:
/typo3-ddev
Or ask Claude:
Set up DDEV for my TYPO3 extension
The skill will:
- Validate prerequisites (DDEV, Docker, TYPO3 extension structure)
- Extract your extension metadata
- Confirm configuration with you
- Generate all
.ddev/files with proper values - Guide you through starting DDEV and installing TYPO3
After setup, you'll have:
project-root/
├── .ddev/
│ ├── config.yaml
│ ├── docker-compose.web.yaml
│ ├── apache/
│ │ └── apache-site.conf
│ ├── web-build/
│ │ └── Dockerfile
│ └── commands/
│ └── web/
│ ├── install-v11
│ ├── install-v12
│ ├── install-v13
│ └── install-all
├── Classes/
├── Configuration/
├── ext_emconf.php
└── composer.json
Once installed, access TYPO3 at:
Overview Dashboard:
https://your-ext.ddev.site/
TYPO3 11.5 LTS:
- Frontend:
https://v11.your-ext.ddev.site/ - Backend:
https://v11.your-ext.ddev.site/typo3/
TYPO3 12.4 LTS:
- Frontend:
https://v12.your-ext.ddev.site/ - Backend:
https://v12.your-ext.ddev.site/typo3/
TYPO3 13.4 LTS:
- Frontend:
https://v13.your-ext.ddev.site/ - Backend:
https://v13.your-ext.ddev.site/typo3/
Username: admin
Password: Password:joh316
The skill creates these custom commands:
# Install specific TYPO3 version
ddev install-v11 # TYPO3 11.5 LTS
ddev install-v12 # TYPO3 12.4 LTS
ddev install-v13 # TYPO3 13.4 LTS
# Install all versions at once
ddev install-all
# Install Introduction Package (demo content)
ddev install-introduction v13Test your extension with realistic content using the TYPO3 Introduction Package:
# Install Introduction Package
ddev install-introduction v13Includes:
- 86+ pages with example content
- 226+ content elements (text, images, forms, tables)
- Multi-language support (EN, DE, DA)
- Bootstrap Package responsive theme
- Perfect for testing RTE features
For extensions needing additional setup (RTE config, TSconfig, TypoScript), create a custom configuration command:
# Copy template
cp .ddev/templates/commands/web/configure-extension.optional \
.ddev/commands/web/configure-myext
# Customize for your extension's needs
# Add: RTE YAML, Page TSConfig, TypoScript, site package setup
# Run after TYPO3 installation
ddev configure-myext v13Use Cases:
- RTE/CKEditor plugins - Configure toolbar, import plugin YAML
- Backend modules - Set up TSconfig, permissions
- Frontend plugins - TypoScript configuration, example content
Pattern Benefits:
- One-command post-install setup
- Consistent team configuration
- Includes demo content automatically
- Reduces manual configuration errors
See SKILL.md for detailed examples and template structure.
If reinstalling TYPO3:
ddev mysql -e "DROP DATABASE IF EXISTS v13; CREATE DATABASE v13;"
ddev install-v13Check and restart services:
docker ps --filter "name=ddev-your-ext"
ddev restartFlush caches:
ddev exec -d /var/www/html/v13 vendor/bin/typo3 cache:flushThe setup creates a unique multi-version environment:
- Extension Source: Mounted at
/var/www/{{EXTENSION_KEY}}(your project root) - TYPO3 Installations: Separate directories for each version (
/var/www/html/v11,v12,v13) - Extension Installation: Installed via Composer path repository in each TYPO3 version
- Persistent Data: Docker volumes for each TYPO3 version database and files
This architecture allows you to:
- Develop extension code in your project root
- Test immediately across all TYPO3 versions
- Keep TYPO3 installations separate and clean
- Avoid committing TYPO3 core files to your extension repository
By default, the skill supports:
- TYPO3 11.5 LTS (PHP 8.0+)
- TYPO3 12.4 LTS (PHP 8.1+)
- TYPO3 13.4 LTS (PHP 8.2+)
PHP version is set to 8.2 for maximum compatibility.
After generation, you can customize:
PHP Version (.ddev/config.yaml):
php_version: "8.3" # Change to 8.1 or 8.3 if neededXDebug (enable/disable):
ddev xdebug on # Enable
ddev xdebug off # DisableDatabase (Tiered Selection: SQLite/MariaDB/PostgreSQL/MySQL):
The skill uses intelligent tiered database selection based on extension complexity:
🎯 Tier 1: SQLite (Simple Extensions - Development Optimized)
For extensions using only TYPO3 Core APIs (no custom tables, no raw SQL):
# No .ddev/config.yaml database config needed
# TYPO3 installation automatically uses SQLiteBenefits:
- ⚡ Startup: 5-10 seconds faster per ddev start
- 💾 RAM: 900 MB saved (no container)
- 💿 Disk: 744 MB saved
- 🔒 Perfect v11/v12/v13 isolation
🔧 Tier 2: MariaDB 10.11 (Complex Extensions - Production Parity)
For extensions with custom tables, raw SQL, or unknown complexity:
# Default for complex extensions (.ddev/config.yaml)
database:
type: mariadb
version: "10.11"Why MariaDB 10.11? Production standard (95% hosting), extension compatibility, 13-36% faster than MySQL 8.
🌐 Tier 3 & 4: Specialized Databases
# PostgreSQL 16 (for GIS, analytics, full-text search)
database:
type: postgres
version: "16"
# MariaDB 11 (forward-looking performance)
database:
type: mariadb
version: "11.4"
# MySQL 8.0 (corporate/Oracle ecosystem)
database:
type: mysql
version: "8.0"For detailed rationale, see docs/adr/0002-mariadb-default-with-database-alternatives.md.
Caching Service (Valkey or Redis):
The skill provides Valkey 8 as the default caching service (open source, future-proof):
# Default: Valkey 8
cp .ddev/templates/docker-compose.services.yaml.optional .ddev/docker-compose.services.yaml
# Alternative: Redis 7 (for legacy production parity)
cp .ddev/templates/docker-compose.services-redis.yaml.optional .ddev/docker-compose.services.yaml
# Restart DDEV
ddev restartWhy Valkey? True open source (BSD-3), AWS/Google/Oracle backing, 30% smaller than Redis 8, cost-effective. See docs/adr/0001-valkey-default-with-redis-alternative.md for details.
Additional Services (add to .ddev/docker-compose.services.yaml):
# The services template includes: Valkey/Redis, MailPit, Ofelia
# See SKILL.md for complete documentationPort Conflicts:
# Check what's using ports 80/443
sudo lsof -i :80
sudo lsof -i :443
# Option 1: Stop conflicting services
# Option 2: Change ports in .ddev/config.yaml
router_http_port: "8080"
router_https_port: "8443"Check Composer Issues:
ddev ssh
composer diagnoseView Installation Logs:
ddev logsRetry Installation:
# For specific version
ddev ssh
rm -rf /var/www/html/v13/*
exit
ddev install-v13Verify Extension Key:
ddev ssh
echo $EXTENSION_KEY # Should match your ext_emconf.phpCheck Composer Repository:
ddev ssh
cd /var/www/html/v13
composer config repositoriesContributions welcome! Please:
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
This skill is based on the excellent work by Armin Vieweg in ddev-for-typo3-extensions.
MIT License - see LICENSE file for details.
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- TYPO3 Slack: #ddev channel
Made with ❤️ for the TYPO3 Community