On Fri, Aug 5, 2016 at 3:03 PM, Josh Elser <[email protected]> wrote: > Keith Turner wrote: >> >> On Fri, Aug 5, 2016 at 2:48 PM, Josh Elser<[email protected]> wrote: >>> >>> > Thanks for all the points, Keith and Mike. This was very helpful to >>> > me. I >>> > assumed formerly-known-as-Zetten was more about deploying Fluo itself, >>> > but >>> > it seems it is more about the prerequisites for Fluo. I was just >>> > assuming a >>> > bit too much it seems:) >>> > >>> > While it might be a little premature before there is an official >>> > release, I >>> > think instructions on the website for how a user installs/configures >>> > Fluo >>> > would be great and help attract new users. >> >> >> This will happen. Mike has been taking markdown instructions in Fluo >> itself and posting those on the website in the past. This includes >> install instructions. I just put up a PR to remove the links to >> fluo-dev (now called Uno) and zetten (now called Muchos) from those >> install instructions. I think this is a nice improvement. The >> install instructions should not have been pointing to those w/o the >> caveat about not using them for production. But I think its better >> just not pointing to them at all. >> >> https://github.com/apache/incubator-fluo/pull/754 >> > > Thanks for the pointer! > > I think making sure that it is crystal clear that Unos and Muchos can be > used to prepare an environment to run Fluo is important. Will watch that > pull request for future updates.
I agree. I updated both projects introduction in an attempt to better communicate this. https://github.com/astralway/uno https://github.com/astralway/muchos
