-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CLI to support entire developer workflow (entire API?) #80
Comments
Awesome @treeder - I'd really love to see this fleshed out. Step 1 of missing functionality is the ability to list out my workers in order to use the CLI further. I can't do anything useful without this part. Sticking with the same syntax that exists now, I'd expect an Example:
Hey @nanliu, we had a good conversation about this after comparing to Heroku and GCE commands. Anything in particular missing for you? |
It may also be helpful to refer to Heroku as an example of a robust CLI you can aim for parity with: https://devcenter.heroku.com/articles/using-the-cli Those it's a little counterintuitive as a syntax. I prefer Docker's structure (and use of environmental variables): https://docs.docker.com/engine/reference/commandline/cli/ |
Two more things that comes to mind:
|
Thanks guys! Very helpful feedback. @Nyarum can you add one for the login? I like that. Perhaps user can set the login credentials for each directory they are in, similar to heroku since each directory would most likely be a different project. @nanliu we don't have access to instances, the system doesn't really work that way. |
There should be no need to use HUD, user should be able to use the cli to interact without going to HUD. This may mean to support the entire API in an intuitive way.
The text was updated successfully, but these errors were encountered: