sails.js

I'm trying to build a chat application based on sails.js. The url for messages from a specific chat looks like this: /api/chat/:id/messages When I request this url with XHR, it provides a session cookie and sails.js builds a session object. I can easily check user rights to read the messages from the specific chat. However, I need to request this url with socket.io so that the client can subscribe to all future changes of the messages collection. When I request this url with socket.io, no session cookie is set and the sails.js session is empty. So, I cannot check the user rights on the server

Does anyone have ideas on maintaining multiple versions of your API when using sails.js? Imagine a simple example like: // Request GET /api/v1/catVids?min_view_count=10000 // Response [{"video_title": "top cat fails"}, {"video_title": "funny-ass cats"}] Users are actively consuming v1 of the API but something has now changed in the requirements that will break existing functionality. For example, an attribute name change. So now we need to utilize a different controller to fulfill requests for this new behavior. What I would like to do is have both APIs co-exist so backwards compatibility is

Sails.js uses the MVC pattern for Node.js and I was wondering if Mocha could be hooked up for testing Models. I know you asked this awhile ago, but I was searching around myself and there's not much out there at the moment. I figured I'd drop what I found into this answer... I found some discussion on the sails github and a gist with some example code. There is also a second discussion with more examples. Check out wolfpack . It's a SailsJS model-testing library that allows you to test Sails models without the need for a db or lifting your sails app. 来源： https://stackoverflow.com/questions

I am new to SailsJs and Socket IO. I want to execute the below Socket IO example in Sailsjs. In the server side, I need to execute the following code. But I dont know where to place this code. var io = require('socket.io').listen(80); io.sockets.on('connection', function (socket) { socket.emit('news', { hello: 'world' }); socket.on('my other event', function (data) { console.log(data); }); }); I am aware that I can place this inside the Cntroller's function but it will add listener to every request which I dont want. Client Side: var socket = io.connect('http://localhost'); socket.on('news',

Using Waterline ORM from SailsJS, my defaults for autoCreatedAt and autoUpdatedAt are set to false, but I still need to implement to the functionality just using different field names (DBA request). Is there a way to either: specify different column names for the automatically generated field, or manually emulate the same behave in an attribute definition, or can I just leave custom fields in the schema like created_ts and updated_ts to be updated with triggers in the DB schema itself (but I still need Waterline to read them)? Thanks in advance. Tristan Foureur I just opened two pull requests

I was looking at using Sails for an app that we are developing. I'm using the sails-postgresql adapter which uses the waterline orm. I have an existing database that I want to connect to. If I create a model using generate something and then in my model I have attributes:{ title:{type:'String'} } If I browse to localhost/something the orm deletes all the columns in the something table except title. Is there a way to stop it from doing this? This app should not delete columns on this database. Thanks! I am the author of Sails-Postgresql. Sails has an ORM called Waterline that it uses for