Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[0.10.0-rc9] "sails.config.express is deprecated; use sails.config.http instead." warning when sails.config.express is never set in my code #1974

Closed
blah238 opened this issue Jul 18, 2014 · 6 comments

Comments

@blah238
Copy link

blah238 commented Jul 18, 2014

I updated from rc8 to rc9 just now and get this warning upon lifting, however I do not have any references to sails.config.express anywhere in my codebase. Is there somewhere I should be looking to change this or is it just an internal sails artifact?

@16n
Copy link

16n commented Jul 19, 2014

I do have the exact same problem.

@davesag
Copy link
Contributor

davesag commented Jul 20, 2014

I had that issue - I am using Passport to manage user authentication and in my config/passport.js I just changed

express: { ... }

to

http: { ... }

and then it worked fine.

@16n
Copy link

16n commented Jul 20, 2014

That did the trick. Thanks!

@kaiomagalhaes
Copy link

I have the same problem, but the tick that davesag comment dont work for me, I'm doing the deploy on nodejitsu and with davesag trick now is showing the messages:

info: Starting app projetocontabillaion
error: Error running command deploy
error: Errors occured while starting the application
error: Error output from application. This is usually a user error.
error: Warning: connection.session() MemoryStore is not
error: designed for a production environment, as it will leak
error: memory, and will not scale past a single process.
error: express midleware for passport
error:
error: Error starting application. This could be a user error.
error: info: Running start for app.
error: info: Reading package.json...
error: info: Starting application...
error: info: Spawn: start --min-uptime 2000 -o /opt/run/forza.log -- forza -h multiplex.nodejitsu.com -p 8556 --start-log /opt/run/start.log --app-user bananananica --app-name projetocontabillaion -- node app.js
error: info: aeternum pid: 326
error: info: Writing pidfile: /root/app.pid
error: info: Tailing forza log: /opt/run/start.log
error: info: Tail closing..
error: info: Retry # 1 with 1000ms interval
error: info: Tailing forza log: /opt/run/start.log
error: info: Tail closing..
error: info: Retry # 2 with 4111ms interval
error: info: Tailing forza log: /opt/run/start.log
error: info: Tail closing..
error: info: Retry # 3 with 12702ms interval
error: info: Tailing forza log: /opt/run/start.log
error: info: Tail closing..
error: info: Success:start
error:

@blah238
Copy link
Author

blah238 commented Jul 20, 2014

@davesag's suggestion worked for me as well. not sure what the deal is with the above though, sounds like a separate issue.

@blah238 blah238 closed this as completed Jul 20, 2014
@davesag
Copy link
Contributor

davesag commented Jul 20, 2014

I'd venture to suggest that the issues @kaiocristianc is facing are entirely separate to the express vs http issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants