Completely agree on the UI being a boon for helping people "get" NiFi.
So, there are a few ways to tackle this, and perhaps this will help us figure out where such things belong with the project. Live demo would be awesome, but the costs of hosting, security, are nontrivial factors to account for. What might strike an interesting balance, but would be a significant undertaking, would be to create an emulated environment in the browser, like a lot of sites use for demos. Vagrantfiles would certainly be helpful, especially for developers in getting a VM up and running with properly tuned settings. We have a couple Docker images floating around. Tony made one with the initial release and I have started one inspired by that work that is available via the Docker Hub Registry [1] with source available, for the time being at [2] in fulfillment of NIFI-153[3]. There was some discussion of how to do this the "right" way in the Apache process, that did not lead to any best practice. Regardless, all of these notions are good ones. [1] https://registry.hub.docker.com/u/aldrin/apache-nifi/ [2] https://github.com/apiri/dockerfile-apache-nifi [3] https://issues.apache.org/jira/browse/NIFI-153 On Wed, May 13, 2015 at 10:01 AM, Joe Witt <[email protected]> wrote: > All, > > Yesterday I had a chance to talk to a really cool startup with awesome > developers who gave some great feedback on nifi. One of the things > they mentioned was how much they loved the UI. In fact they said if > they hadn't seen the reference to the UI they would have said > 'interesting' and moved on but not really followed up. > > The point they made is we should make it as easy as possible to get > from landing on the apache nifi webpage to having an up and running > instance of NiFi for them to get to start playing with the UI. > > I'd like to put this out there to get a sense of how people see this > being most effectively done. > > They mentioned Vagrant. We've also had some folks mention and > contribute references to docker images. Other ideas might be > providing a live/running site where people could just immediately > start gaining familiarity with nifi. > > Each of these have different pros/cons and it is unclear how to do > these in apache effective ways. > > Look forward to ideas you all may have or thoughts on what other > effective approaches projects have taken. > > Thanks > Joe >
