How the heck do you start and view the demo?

[facultymatt]

I cd into the example folder, and run sails lift and everything appears to start... but I can't figure out what port the app is running on...

Seems simple enough but for a demo this should be made 100 percent obvious... readme maybe?

[ChrisChares]

Edit: I have a feeling you might be looking for this instead https://github.com/balderdashy/sails

[facultymatt]

Yes and no... I am trying to use the angularSails library for integration with angular...

There is an example in the project, /example which I tried to run. It looks to be a full sails app, but when I run it I get the following:

sails lift

info: Starting app...


debug: NOTE:
debug: This app depends on an unreleased version of Sails:
debug: git://github.com/balderdashy/sails.git

warn: `sails.config.express` is deprecated; use `sails.config.http` instead.
verbose: logger hook loaded successfully.
verbose: request hook loaded successfully.
verbose: Loading the app's models and adapters...
verbose: Loading app models...
verbose: Loading app adapters...
silly: Building action for view:  403
silly: Building action for view:  404
silly: Building action for view:  500
silly: Building action for view:  homepage
silly: Building action for view:  layout
verbose: Loading blueprint middleware...
verbose: blueprints hook loaded successfully.
verbose: Loading runtime custom response definitions...
verbose: responses hook loaded successfully.
verbose: controllers hook loaded successfully.
verbose: Loading policy modules from app...
verbose: Finished loading policy middleware logic.
verbose: policies hook loaded successfully.
verbose: Loading app services...
verbose: services hook loaded successfully.
verbose: csrf hook loaded successfully.
verbose: cors hook loaded successfully.
  i18n:debug will write to /Users/spmatt/sites/labs/angularSails/example/config/locales/en.json +0ms
  i18n:debug read /Users/spmatt/sites/labs/angularSails/example/config/locales/en.json for locale: en +0ms
  i18n:debug will write to /Users/spmatt/sites/labs/angularSails/example/config/locales/es.json +0ms
  i18n:debug read /Users/spmatt/sites/labs/angularSails/example/config/locales/es.json for locale: es +0ms
  i18n:debug will write to /Users/spmatt/sites/labs/angularSails/example/config/locales/fr.json +0ms
  i18n:debug read /Users/spmatt/sites/labs/angularSails/example/config/locales/fr.json for locale: fr +0ms
  i18n:debug will write to /Users/spmatt/sites/labs/angularSails/example/config/locales/de.json +1ms
  i18n:debug read /Users/spmatt/sites/labs/angularSails/example/config/locales/de.json for locale: de +0ms
verbose: i18n hook loaded successfully.
verbose: session hook loaded successfully.
verbose: Loading app Gruntfile...
verbose: Tracking new grunt child process...
verbose: grunt hook loaded successfully.
connect deprecated methodOverride: use method-override npm module instead node_modules/sails/lib/hooks/http/middleware/defaults.js:164:34
verbose: http hook loaded successfully.
verbose: Overriding ejs engine config with ejslocals to implement layout support...
verbose: Configuring socket (ws://) server...
verbose: sockets hook loaded successfully.
verbose: Loading user hooks...
verbose: views hook loaded successfully.
verbose: Setting default Express view engine to ejs...
verbose: Located 0 user hook(s)...
verbose: Loading adapter ( sails-disk ) for comment  from `node_modules` directory...
verbose: Initialized 0 user hook(s)...
verbose: userhooks hook loaded successfully.
-----------------------------------------------------------------

 Excuse my interruption, but it looks like this app
 does not have a project-wide "migrate" setting configured yet.
 (perhaps this is the first time you're lifting it with models?)

 In short, this setting controls whether/how Sails will attempt to automatically
 rebuild the tables/collections/sets/etc. in your database schema.
 You can read more about the "migrate" setting here:
 http://sailsjs.org/#/documentation/concepts/ORM/model-settings.html?q=migrate

 In a production environment (NODE_ENV==="production") Sails always uses
 migrate:"safe" to protect inadvertent deletion of your data.
 However during development, you have a few other options for convenience:

 1. safe  - never auto-migrate my database(s). I will do it myself (by hand)
 2. alter - auto-migrate, but attempt to keep my existing data (experimental)
 3. drop  - wipe/drop ALL my data and rebuild models every time I lift Sails

What would you like Sails to do?

info: To skip this prompt in the future, set `sails.config.models.migrate`.
info: (conventionally, this is done in `config/models.js`)

warn: ** DO NOT CHOOSE "2" or "3" IF YOU ARE WORKING WITH PRODUCTION DATA **

prompt: ?:  verbose: Grunt :: Running "clean:dev" (clean) task
verbose: Grunt :: Cleaning ".tmp/public"...
verbose: Grunt :: OK
verbose: Grunt :: Running "jst:dev" (jst) task
verbose: Grunt :: >> Destination not written because compiled files were empty.
verbose: Grunt :: Running "less:dev" (less) task
verbose: Grunt :: File .tmp/public/styles/importer.css created.
verbose: Grunt :: Running "copy:dev" (copy) task
verbose: Grunt :: Created 1 directories
verbose: Grunt :: , copied 20 files

Running "coffee:dev" (coffee) task
verbose: Grunt :: Running "sails-linker:devJs" (sails-linker) task
verbose: Grunt :: padding length 4
verbose: Grunt :: File "views/layout.ejs" updated.

Running "sails-linker:devStyles" (sails-linker) task
verbose: Grunt :: padding length 4
verbose: Grunt :: File "views/layout.ejs" updated.
verbose: Grunt :: Running "sails-linker:devTpl" (sails-linker) task
verbose: Grunt :: padding length 4
verbose: Grunt :: File "views/layout.ejs" updated.
verbose: Grunt :: Running "watch" task
verbose: Grunt :: Waiting...

And then http://localhost:1337/ says web page not available.

Any thoughts?

[ChrisChares]

Yeah I guess the example was trying to install Sails directly from Github instead of a versioned release. I fixed that in my fork if you still want to launch the example https://github.com/ChrisChares/angularSails

There is also a generator project to generate new Sails apps with Angular built in from scratch. https://github.com/chiefy/sails-generate-controller-angular

That project won't install this $sailsSocket service by default though. Easily included with

$ bower install --save angularSails

[pablomoran]

@ChrisChares Hey! your problem is that the console is expecting you to enter a response for:
In a production environment (NODE_ENV==="production") Sails always uses
migrate:"safe" to protect inadvertent deletion of your data.
However during development, you have a few other options for convenience:

1. safe - never auto-migrate my database(s). I will do it myself (by hand)
2. alter - auto-migrate, but attempt to keep my existing data (experimental)
3. drop - wipe/drop ALL my data and rebuild models every time I lift Sails

What would you like Sails to do?

You need to insert a response like: 1
then hit enter.

To avoid this in the future just go into the example/config/models.js and make sure it looks like this:
module.exports.models = {

// Your app's default connection.
// i.e. the name of one of your app's connections (see config/connections.js)
//
// (defaults to localDiskDb)
connection: 'localDiskDb',
migrate: 'safe' // ADD THIS (MAKE SURE TU INCLUDE THE COMMA IN THE PREVIOUS LINE)
};

[pablomoran]

Anyways... This will grant you access to localhost:1337... but not to the contents of the www folder.

How can I access the ANGULAR views in this app?

[ChrisChares]

@pablomoran Heyo, that is correct. I ended up putting the migrate: 'drop' line into the connection.js config on my fork. Probably should change that to 'alter' though in retrospect. I figured it was better to streamline options so someone who just wants to see the example in action doesn't have to understand migration settings.

[ChrisChares]

@pablomoran All front end resources (angular views, styles, images, scripts etc) live in the /assets folder. Upon run sails processes these files (linking, less compiling, minification in production, etc) and copies them to the .tmp/www folder, where it is served from. Do all your front end coding on files in the /assets folder.

EDIT: I should probably add that the root /views folder does not contain Angular views. That folder holds the EJS/Jade templates sails would normally be using. However, some projects still uses /views/layout.ejs as the root view containing the ng-app, ui-view directives etc. generator-sails-angular does this