martijndeh / fire Goto Github PK

Hi,

I'm setting up a new project but somehow the grunt build stopped somewhere.
Maybe I installed incorrectly?
It looks like the api and script subtasks are never called...

output:

Running "build:migrations" (build) task
fire:app Not loading module SEO. +0ms
fire:app Adding module templates. +0ms
fire:app Adding module models. +0ms
fire:app Not loading module Static. +0ms
fire:app Adding module controllers. +0ms
fire:bridge Setting app.animation(...). +0ms
fire:bridge Setting app.config(...). +0ms
fire:bridge Setting app.constant(...). +0ms
fire:bridge Setting app.directive(...). +0ms
fire:bridge Setting app.factory(...). +0ms
fire:bridge Setting app.filter(...). +0ms
fire:bridge Setting app.provider(...). +0ms
fire:bridge Setting app.service(...). +0ms
fire:app Adding module bridge. +1ms
fire:app Adding module API. +0ms
fire:app Not loading module Workers. +0ms
fire:app Not loading module HTTPServer. +0ms
fire:app Not loading module ConfigureFunctions. +0ms
fire:app Not loading module Tasks. +0ms
fire:app Not loading module WebSockets. +0ms
fire:app Adding module channels. +0ms
fire:app Adding module moduleProperties. +0ms
fire:app App#start +0ms
fire:app Cancelling App#start because of app disabled +0ms
fire:models Models::setup +0ms
fire:sql SELECT * FROM pg_extension WHERE extname = $1 (uuid-ossp) +0ms
fire:controllers addController TestController +0ms
fire:generate Old models setup. +0ms
fire:models Models::setup +13ms
fire:sql SELECT * FROM pg_extension WHERE extname = $1 (uuid-ossp) +12ms
fire:generate Loading migrations to oldModels from /Users/arjanvandijk/WebstormProjects/NOF/_migrations. +1ms
fire:generate Reseting migration-models +0ms
fire:migration Migrations#resetAllModels +0ms
fire:generate Soft migrating to 0 +1ms
fire:generate Creating migration tasks +0ms
Your local migrations are up-to-date.
Arjans-MacBook-Pro:NOF arjanvandijk$

Automatically creating new migrations based on model changes is what every node developer coming from Django has been looking for.

Hi there, I'm having trouble creating a model with a different name for the id primary key field.

Is this just how the ORM works? And I can't do something like:

this.id = undefined;
this.other_id = [this.Id];

Cheers.

Request:

It would be great if there was a function that create an instance of a model including including all the properties with default values, calculated fields aso.

(maybe such a function is already there?)

ps. I'm studying on the code at the moment...

Hi Martijn,

I get the following error when starting the app in browser

Error: [$location:nobase] http://errors.angularjs.org/1.3.0/$location/nobase
at Error (native)
at http://localhost:3000/bower_components/angular/angular.min.js:6:416
at He.$get (http://localhost:3000/bower_components/angular/angular.min.js:97:402)
at Object.e as invoke
at http://localhost:3000/bower_components/angular/angular.min.js:38:244
at d (http://localhost:3000/bower_components/angular/angular.min.js:36:165)
at Object.e [as invo

I changed it locally to

$locationProvider.html5Mode({
enabled: true,
requireBase: false
});

or have a baseref='/' in html.

It's related to angular 1.3.0

Hey there. I am currently reviewing your implementation, and I'm mainly just curious as to why you are not using the pg.native bindings? See the "Native Bindings" section here: https://github.com/brianc/node-postgres for more details.

When trying to run the 'fire release' step for the multi-apps example, I get the following error:

fire release
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn node_modules/.bin/grunt ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
at child_process.js:1144:20
at process._tickCallback (node.js:355:11)
at Function.Module.runMain (module.js:503:11)
at startup (node.js:129:16)
at node.js:814:3

Then, if I try to use 'grunt release' straight off, I see:

grunt release
Running "release:migrate" (release) task
relation "schemas" does not exist
error: relation "schemas" does not exist
at Connection.parseE (/home/kierer/dev/fire/examples/multiple-apps/node_modules/fire/node_modules/pg/lib/connection.js:534:11)
at Connection.parseMessage (/home/kierer/dev/fire/examples/multiple-apps/node_modules/fire/node_modules/pg/lib/connection.js:361:17)
at Socket. (/home/kierer/dev/fire/examples/multiple-apps/node_modules/fire/node_modules/pg/lib/connection.js:105:22)
at Socket.emit (events.js:107:17)
at readableAddChunk (_stream_readable.js:163:16)
at Socket.Readable.push (_stream_readable.js:126:10)
at TCP.onread (net.js:538:20)
Fatal error: relation "schemas" does not exist

I initially thought it might be a case issue brought on by the quoting of the relation name on creation, but I checked the example source and case is consistent for "schemas"; I see that there was a similar issue that was resolved going into 0.28.2, however.

I had installed npm, fire, and postgresql and pgadmin3 on an RHEL6 virtual machine,
and then rebooted just to make sure.
Then I tried to create my first app:
fire apps:create helloworld

events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)
Why does this fail? Thanks.

Hi,

Due to busy times I didn't had the opportunity to dive in nodeonfire but now I'm back on track again...
I was looking into the virtual and readonly properties and I was wondering if it is possible to create a read-only property based on related objects?

thx
Arjan

Hi there,

I've just installed node on fire, created an app and tried to run it. The following is the resulting error :

sudo fire run
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn node_modules/fire/node_modules/.bin/nf ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:452:9)
    at process._tickCallback (node.js:366:17)
    at Function.Module.runMain (module.js:459:11)
    at startup (node.js:138:18)
    at node.js:974:3

I'm currently running node 5.1.0 on macOS, but I have tried 4.2.2 LTS as well.