Date: Fri Sep 5 14:43:25 MDT 2025
Directory: /Users/rfay/workspace/d11
Git HEAD: 060a2d2d
Total Add-ons: 159
| # | Add-on | GET | REMOVE | Clean | Notes |
Studying the problem on wsl-14, | |
The healthcheck says " "Output": "Traefik healthcheck failed: Detected 2 configuration error(s) in project" but it doesn't say what they are, which would be an improvement. | |
The log says | |
``` | |
2025-08-26T11:11:26-06:00 ERR EntryPoint doesn't exist entryPointName=http-80 routerName=TestPkgDrupal11-web-80-http@file | |
2025-08-26T11:11:26-06:00 ERR No valid entryPoint for this router routerName=TestPkgDrupal11-web-80-http@file | |
2025-08-26T11:11:26-06:00 ERR EntryPoint doesn't exist entryPointName=http-443 routerName=TestPkgDrupal11-web-80-https@file | |
2025-08-26T11:11:26-06:00 ERR No valid entryPoint for this router routerName=TestPkgDrupal11-web-80-https@file |
This documents a complete demonstration of DDEV's Traefik router routing TCP traffic using SNI (Server Name Indication) based routing. We successfully demonstrated the concept using a simple NetCat listener, then explored MySQL limitations.
=== DDEV Add-on Ecosystem Analysis === | |
Total repositories with topic:ddev-get: 145 | |
=== Checking for advanced features usage === | |
=== SUMMARY STATISTICS === | |
Advanced Features Usage: | |
yaml_read_files: 0 add-ons | |
Go templating: 0 add-ons |
This refactoring transforms the DDEV remote config system from a single-purpose, hardcoded solution into a flexible, generic system capable of downloading arbitrary JSONC files from GitHub repositories. Most importantly, it adds the first comprehensive test coverage for the remote config system, which previously had zero tests.
The original remote config system had several limitations:
ddev/remote-config/remote-config.jsonc
A bash script to systematically check for missing PHP packages in the Sury PHP repository for Debian distributions.
This script helps identify missing PHP packages across different PHP versions and architectures in the Sury repository. It's particularly useful when experiencing package availability issues on newer Debian distributions.
DDEV's current add-on ecosystem has two key weaknesses:
install.yaml
relies on locally installed tools (primarily bash), but bash capabilities vary across environments, leading to inconsistent success ratesThis proposal outlines an approach to enable Go-based actions as an alternative technique for DDEV add-ons, while maintaining full support for existing bash-based actions. Both techniques will be equally supported, and add-on developers can choose the approach that best fits their needs. The solution uses Docker containers with Go runtime to build and execute Go source files on-demand, requiring only Docker (which DDEV already requires) on user machines.
DDEV add-ons currently use install.yaml
with bash scripts:
======== Output file will be in /var/folders/_d/d66tr_cj5j1dq9gjr1rftddr0000gn/T/ddev-debug-test.txt ======== | |
======== Existing project config ======== | |
ddev installation alternate locations: | |
/usr/local/bin/ddev | |
/opt/homebrew/bin/ddev | |
/usr/local/bin/ddev |
{ | |
"name": "DDEV Devcontainer setup", | |
"image": "mcr.microsoft.com/devcontainers/base:latest", | |
"workspaceFolder": "/var/www/html", | |
"settings": { | |
"terminal.integrated.cwd": "/var/www/html" | |
} | |
} |