Cannot run with forever js

[SuThaw]

I installed forever js with
"npm install forever -g"
and I run like this
forever start app.js --prod

nothing happen , when i check with forever list there is a process running. But it doesn't work. What is wrong??

[RWOverdijk]

What do you mean with "doesn't work"? Because for me it works just fine.
Please follow these steps:

1. Set the log level to verbose in config/log.js
2. Run the application with forever. forever start app.js
3. Figure out where the log file is. forever list
4. Tail the log file to figure out what's happening. tail -f /home/my-user/.forever/fz6i.log
5. If you still can't figure out why it's broken, paste the results (console output) here.

[SuThaw]

here is the screen shot

[SuThaw]

The server is not started and when i access to localhost:1337 , it get nothing

[RWOverdijk]

You didn't do everything I asked.

[SuThaw]

[SuThaw]

in the log it is just waiting

[RWOverdijk]

It should be waiting.

Are you running it on your local machine? If so, what do you see when you go to http://127.0.0.1:1337 ?

[SuThaw]

This webpage is not available It is also not work on my vps. It is the same.

[RWOverdijk]

I can not reproduce this. does running node app.js work? As in, does it then show in the browser?

[SuThaw]

it is working with node app.js. Just only not work with forever.js. Is there something wrong in when i create the project. I installled the sails globally and start the project with "sails new project-name --linker'

[RWOverdijk]

I can't reproduce this. Another question, follow the steps I mentioned before. In stead of doing tail -f, do a cat, and paste the results, as in all of it, on http://gist.github.com

1. Stop any processes forever stop app.js
2. Start a new one forever start app.js
3. Figure out where the log file is. forever list
4. Dump the log cat path/to/log/from/step/3
5. Paste results

[SuThaw]

https://gist.github.com/SuThaw/8382f453220ffd57c676

[RWOverdijk]

@SuThaw

 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 **

You have migrate set to (I think) nothing. Open up config/models.js and add migrate: 'safe'.

Optionally, you can choose between these migration options:

• safe - Don't do anything
• alter - Alter the tables, and try to keep the data in them
• drop - Drop all tables, and their data, and rebuild them using the new model definitions.

[SuThaw]

@RWOverdijk Thanks a lot. I got it. Thanks for your advice.