docs: clarify usage for TUI#8203
Merged
Merged
Conversation
|
Download the artifacts for this pull request:
See Testing a PR.
|
rfay
approved these changes
Mar 4, 2026
rfay
left a comment
rfay
left a comment
Member
There was a problem hiding this comment.
It looks great, thanks.
I think we probably ought to use "dashboard" more and "tui/TUI" less, as people don't seem to know what it is.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Issue
We still say to use
ddevwithout arguments in several places, but it's replaced by TUI.How This PR Solves The Issue
ddev/ddev helpusageddev tuito the docsno_tuioption in the config docsno_tuito the globalschema.jsonManual Testing Instructions
Automated Testing Overview
Release/Deployment Notes