rfay

rfay@rfay-hp:~/tmp/x$ ddev config --project-type=drupal12 --docroot=web
Creating a new DDEV project config in the current directory (/home/rfay/tmp/x)
Once completed, your configuration will be written to /home/rfay/tmp/x/.ddev/config.yaml

Created docroot at /home/rfay/tmp/x/web
Configuring a 'drupal12' project named 'x' with docroot 'web' at '/home/rfay/tmp/x/web'.
For full details use 'ddev describe'.
No settings.php file exists, creating one
Configuration complete. You may now run 'ddev start'.
rfay@rfay-hp:~/tmp/x$ ddev composer create-project   --repository='{"type":"vcs","url":"https://github.com/rfay/

rfay

2025-08-13 7883
2025-08-14 7883
2025-08-15 7908
2025-08-16 7908
2025-08-17 7908
2025-08-18 7908
2025-08-19 7908
2025-08-20 7913
2025-08-21 7913
2025-08-22 7918

rfay

PR #7558 Manual Testing Report

Test Prompt

Here we're working on ddev/ddev#7558 and we need to use the executable built here. That is all set up fine.

• You can create test projects in ~/tmp as needed
• The manual testing instructions are excellent. They refer to DDEV's quickstarts, which are here in quickstart.md
• We need to do the quickstart builds, as it says in the instructions, then run the manual testing that is suggested
• A report will be done then
• Do these evaluations one at a time, with an intermediate report after each one.

rfay

DDEV Add-on Test Report

Date: Fri Sep 5 14:43:25 MDT 2025
Directory: /Users/rfay/workspace/d11
Git HEAD: 060a2d2d
Total Add-ons: 159

Results

| # | Add-on | GET | REMOVE | Clean | Notes |

rfay

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

rfay

DDEV Traefik TCP Routing with SNI - Complete Demonstration and Analysis

Overview

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.

Successful NetCat Demonstration

Configuration Files

1. NetCat Listener Setup

rfay

=== 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

rfay

DDEV Remote Config Refactoring: Arbitrary JSONC Downloads + Comprehensive Testing

Overview

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.

Problem Statement

The original remote config system had several limitations:

• Hardcoded: Could only download ddev/remote-config/remote-config.jsonc

rfay

deb.sury.org Missing Packages Checker

A bash script to systematically check for missing PHP packages in the Sury PHP repository for Debian distributions.

Purpose

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.

Usage

rfay

DDEV Add-on Ecosystem Improvements

Problem Statement

DDEV's current add-on ecosystem has two key weaknesses:

1. Complex install.yaml syntax - Advanced add-ons like ddev-platformsh result in unreadable and unmaintainable bash scripts mixed with Go templating
2. Host dependency issues - install.yaml relies on locally installed tools (primarily bash), but bash capabilities vary across environments, leading to inconsistent success rates

Current Architecture Analysis