Also I forgot and am not sure how to better keep up with this, but here is a list of dependancies so far in the new console:
- bootstrap (Apache 2) - angularjs (MIT) - font-awesome fonts (SIL OFL 1.1) - font-awesome code (MIT) - angular ui-bootstrap (MIT) - chartjs (MIT) - blur (Apache 2) All of the Java dependencies are being used from the blur dependencies. On Tue, Oct 8, 2013 at 2:04 PM, Chris Rohr <[email protected]> wrote: > I have pushed up a branch for the blur console work (blur-console-v2). I > have setup a basic structure with some RESTful calls in the Jetty server > and the first two parts of the Dashboard. I will need a lot of help to > flush out the rest of it. We should probably create Jira tickets for each > of the other parts. > > Also, AngularJS has some very good testing ability with Jasmine and Karma > Test Runner, it would be great if I could get some help in wiring that up > to Maven. > > Please everyone take a look and lets talk about how I started this and if > this is how we should continue. > > The legacy (v1) blur console is in the folder blur-console-old for > reference. > > Chris > > > On Tue, Oct 8, 2013 at 9:51 AM, Tim Williams <[email protected]> wrote: > >> On Fri, Oct 4, 2013 at 2:23 PM, Aaron McCurry <[email protected]> wrote: >> > I think that any security concerns about being able to talk to the Blur >> API >> > are all ahead of us. Meaning, if we need to secure the console jetty >> > server then we will have to work that as an issue. Probably something >> like >> > SSL server with some kind of configurable authentication module. Same >> goes >> > for the standard thrift protocols. But I think at this point the relay >> > setup is a good start, and it should allow us to secure things down the >> > road. >> > >> > What do you think? >> >> My vote would be to just post something - a single method call all the >> way through the stack - and punt on the security thing for now. Jetty >> seems like a nice place to do the auth when we get there. Can you >> just push a branch with a single call for now? >> >> --tim >> > >
