You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/blog/2026-plans.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,14 +42,14 @@ In 2025 we established [Board of Directors](board-of-directors-established.md),
42
42
- Consider MCP (for projects) as key DDEV feature
43
43
- Consider MCP for DDEV ([experimental PR](https://github.com/ddev/ddev/pull/7604))
44
44
- Integration of mkcert CA without use of external `mkcert` tool
45
-
- Start a project without ddev config, Consider offering ddev config --auto or ddev config when ddev start in a directory without config ([issue](https://github.com/ddev/ddev/issues/7976))
45
+
- Start a project without `ddev config`, Consider offering `ddev config --auto` or `ddev config` when `ddev start` in a directory without config ([issue](https://github.com/ddev/ddev/issues/7976))
46
46
- Explore using real certificates instead of mkcert CA
47
47
- Subdomains for extra ports/services instead of separate ports. (Prereq for some web-based setups like coder). See the [blog](ddev-expose-node-app-on-subdomain.md) on this approach.
48
48
- Coder support for subdomains. Could codespaces use some proxy/redirect technique to route subdomains to main item, but have a header that determined how traefik would route it?
49
49
- Use a DDEV proxy on the host to allow commands like ddev list and ddev describe and ddev launch to work from inside the web container.
50
50
- Explore moving Mutagen completely into container (syncing between volume and bind-mount)
51
51
- Improved management of `.ddev/.env*` files, marking DDEV-owned lines, etc.
52
-
- More work on web-based setups like coder and codespaces and Dev Containers in general.
52
+
- More work on web-based setups like Coder and Codespaces and Dev Containers in general.
53
53
- Explore environment adjustments that might let users work "inside the web container" as if they were on a real host (use `composer` instead of `ddev composer`, etc). People can already do this with `ddev ssh`, but that isn't directly compatible with VS Code or PhpStorm.
54
54
- Serialize concurrent runs of `ddev start` and similar commands.
55
55
- Move the DDEV IntelliJ/PhpStorm plugin to the DDEV organization.
0 commit comments