Required modifications/extensions to ddev CLI to expose API to front-end dashboard

[rickmanelius]

During the prototype phase, @andrew-c-tran is relying on a thin node server that is running command line exec calls and waiting for/parsing the output before returning the data back. In the future, we would prefer a more persistent connection (potentially through a websocket approach) so that we are using a more robust solution with real time status updates.

[rickmanelius]

I anticipate @beeradb @rfay @tannerjfco being valuable from the perspective of what is possible and/or easy from the Golang side.

[rickmanelius]

At this time, we're not ready to proceed on this until we see the outcome of #9. Tagging and removing from the board.

[rickmanelius]

@andrew-c-tran I think you mentioned having a doc for review. Can you post/link to it here?

[rickmanelius]

It looks like we're now tracking in the following locations:

• ddev config and ddev config <provider> must be executable with flags, not interactive ddev#476
• ddev "api" for interacting with ddev-ui, other future applications, and normal user ddev#477

[rickmanelius]

I'd like to keep this open until the two linked issues are at least in an actionable state and therefore we have a full/complete sense of the LOE.

[rickmanelius]

@andrew-c-tran I'm assuming at this point that this related issue (ddev/ddev#477) fully addresses the API needs for functionality within the v0.1 roadmap. If so, please close this out.

[rfay]

Was completed in ddev/ddev#477