My understanding is that you can run it with the mock API, but using Vagrant gives you the best development experience.
On Mon, Sep 29, 2014 at 2:00 PM, Chris Geer <[email protected]> wrote: > Ok, I guess I'm confused then. Sorry. > > On Mon, Sep 29, 2014 at 10:51 AM, Stanton Sievers <[email protected]> > wrote: > >> It was my understanding the VM wasn't needed to simply get the >> "rave-portal-ng" component working. It uses a mock-api to allow for quick >> UI development. This is what was reviewed (see the e-mail from Matt with >> the recording). >> >> On Mon, Sep 29, 2014 at 1:47 PM, Chris Geer <[email protected]> wrote: >> >> > Then yes you are. Their scripts fire up Rave running inside a virtual >> > machine. >> > >> > On Mon, Sep 29, 2014 at 10:22 AM, Erin Noe-Payne < >> [email protected] >> > > >> > wrote: >> > >> > > I'm not sure what you mean by running it in the vm Chris? I followed >> > > the steps outlined in the readme : >> > > https://github.com/apache/rave/blob/angular/README.txt >> > > >> > > On Mon, Sep 29, 2014 at 11:06 AM, Chris Geer <[email protected]> >> > > wrote: >> > > > Are you running it in the VM? I think there was an issue where the >> > > shindig >> > > > url had to be updated. >> > > > >> > > > On Mon, Sep 29, 2014 at 8:43 AM, Erin Noe-Payne < >> > > [email protected]> >> > > > wrote: >> > > > >> > > >> I also encountered the same problem. >> > > >> >> > > >> On Mon, Sep 29, 2014 at 8:54 AM, Matt Franklin < >> > > [email protected]> >> > > >> wrote: >> > > >> > On Mon, Sep 29, 2014 at 10:31 AM, Stanton Sievers < >> > > [email protected]> >> > > >> > wrote: >> > > >> > >> > > >> >> Hi everyone, >> > > >> >> >> > > >> >> I've been playing around with the Angular branch trying to get >> the >> > > new >> > > >> work >> > > >> >> up and running but I've run into some problems. >> > > >> >> >> > > >> >> From what I can tell, all I need to do is run "npm install" >> (first >> > > time >> > > >> >> only) and then "grunt dev" to build everything. If I follow >> those >> > > >> simple >> > > >> >> steps I end up getting less build errors: >> > > >> >> >> > > >> >> > Running "less:dev" (less) task >> > > >> >> > >> 'bootstrap/less/bootstrap.less' wasn't found. >> > > >> >> > Warning: Error compiling LESS. Use --force to continue. >> > > >> >> > >> > > >> >> > Aborted due to warnings. >> > > >> >> >> > > >> >> I can work around these issues by updating the paths in >> "rave.less" >> > > to >> > > >> use >> > > >> >> the proper relative path to the boostrap resources in >> > > >> >> rave-portal-resources. >> > > >> >> >> > > >> >> At that point, things build but do not run when I go to " >> > > >> >> http://0.0.0.0:8080"; >> > > >> >> I get an error related to this line in "index.html": >> > > >> >> > <script data-main='config/startup', >> > > >> src='requirejs/require.js'></script> >> > > >> >> >> > > >> >> That file does not exist. >> > > >> >> >> > > >> >> I feel like I'm missing something at a high-level here. Has >> anyone >> > > had >> > > >> >> luck getting things to run from the angular branch >> > > >> > >> > > >> > >> > > >> > I am seeing the same issues. Maybe the submitters of that code >> > patch >> > > can >> > > >> > shine some light on the equation. >> > > >> > >> > > >> > >> > > >> >> ? >> > > >> >> >> > > >> >> Thanks, >> > > >> >> -Stanton >> > > >> >> >> > > >> >> > > >> > >>
