Thanks Rodric and Nimbella for contributing the Playground UI to OpenWhisk. This would greatly improve the first user experience trying out OpenWhisk by providing them a good ui to play around with OpenWhisk without installing the `wsk` cli and learning it
For those who want to try this feature now $ wget https://github.com/chetanmeh/incubator-openwhisk/releases/download/0.14/openwhisk-standalone.jar $ java -jar openwhisk-standalone.jar --pg As the Playground provides much simpler experience for the first time user (even does not need `wsk` cli installed) I was thinking to launch Playground UI as a default behavior By default when a user run `java -jar openwhisk-standalone.jar` it would also install the actions needed for Playground use and also launch the browser loading the Playground UI automatically with following conditions 1. Launch PG by default 1. If launch is done from console. Such that test when launching the standalone does not trigger PG flow (should be possible to do by checking for TTY support in Console) 2. If system is configured with `MemoryArtifactStore` or used `--couchdb` option. Idea here being to not automatically install the action if user was connecting to some other long term db. Note that this would need to be later fixed for also preventing default bootstrapping user if standalone is started referring to some existing db managed outside of Standalone lifecycle 2. If user passes `--no-pg` then Playground would not be launched 3. If user explicitly passes `--pg` then Playground would be launched Chetan Mehrotra [1] https://github.com/chetanmeh/incubator-openwhisk/releases/download/v0.14/openwhisk-standalone.jar Chetan Mehrotra On Sat, Oct 12, 2019 at 4:08 AM David P Grove <gro...@us.ibm.com> wrote: > > > > Rodric Rabbah <rod...@gmail.com> wrote on 10/11/2019 05:08:09 PM: > > > > With Chetan's contributions around the standalone controller, he and I > > recently chatted about adding a simple UI to complement all the other > > features now available out of the box. > > > > At Nimbella, we had developed a playground interface for quickly > authoring > > functions (and sharing code) and we'd like to contribute this to the > Apache > > project. > > > > I have opened a PR [1] to seed this implementation and have coordinated > > with Chetan so that it can be used with the standalone controller. You > can > > try it out at [2] if you haven't already seen in and I will show it at > the > > upcoming tech exchange on Wednesday. > > > > Feedback as usual is welcomes and appreciated. I have not considered > adding > > this to the rest of the deployments but could explore that. In particular > a > > previous commit added a "/ui" route to the nginx routing in the open > source > > configuration and we could use that for this purpose. > > > > This is cool! > > Looking forward to the demo at the next tech exchange. > > --dave
