ddev-ui
ddev-ui copied to clipboard
drud
A not-currently-maintained user Interface that provides a graphical way of interacting with DDEV Local
## What happened (or feature request): The --continuous flag was added to ddev list to make it simpler (and lighter-weight) for ddev-ui to check the status of projects. Please change...
## What happened (or feature request): Add from CMS Distro downloads and installs the most latest versions of the CMS selected. However, it was discovered that it pulls the latest...
## What happened (or feature request): Over in https://github.com/drud/ddev/issues/476 we're going to make `ddev config` (the base command) work with flags and skip the interactive path. However, ddev-ui will still...
## What happened (or feature request): We need to have a broader understanding of ddev-ui's code and structure and technologies. The goal would be to have basic architecture docs that...
## What happened (or feature request): The current verbiage of errors, dialogs, and prompts in DDEV-UI have been made up on the fly and may not be the most user...
## What happened (or feature request): ## What you expected to happen: ddev-shell wrapper currently does not use promises nor the -j flag in all calls. To ensure consistency of...
## What happened (or feature request): With https://github.com/drud/ddev/pull/622 we have made the router port configurable, so http and https URLs may have a port suffix if they're not the default....
## What happened (or feature request): Currently there's a complex technique used to try to figure out if a config already exists (a deliberate failure). This is fragile and also...
## What happened (or feature request): Currently the code has inline tests for CMS type, and we are going to be expanding our CMS types very soon. We don't want...
## What happened (or feature request): * Feature request ## What you expected to happen: * The ability to run `ddev exec` commands directly through the GUI. While this is...
