Any thoughts/tips/examples on using sails as the backend API for ember?
Particularly, what is the best why to make the default sails rest format confirm to what ember expects?
Is it maybe better to make ember accept sails format?

I use Sails version 0.10@rc-7 for a realtime Ember app. I started with this adapter and this serializer and “hacked” them together.
I’ve been thinking for a while now to make my versions open source so their quality can be improved a lot.

Hi @ofridagan. There is an unfortunate bug currently with the Ember Sails Adapter where the SailsSocketAdapter uses singular model names in its routes and the the SailsRESTAdapter uses plural model names in its routes. There is a pr that fixes that issue where I’ve been waiting on some feedback but I can merge that now and push out a new release.

I’ve been using Ember Data’s built in JSONSerializer to work around Sails’s lack of a root-element in its response payload. This requires defining your relationships as ‘async’ which have some annoying edge cases in Ember Data at the moment. As a result I’d defiantly suggest go down the path of using @m19’s serializer.

I am very interested in using Sails.js as the backend as well and will probably try it for one of the next projects. Good to see that there is some more interested. Even though I have seen the ember-sails-adapter my strategy would probably to create a blueprint to change it on the server-side (don’t like doing that kind of stuff on the client-side if I have control over the API).

@GlobeCoder Also curious about your Sails blueprints for Ember, since I’m more or less half way through writing/modifying my own blueprints and I also thought about releasing them open source. Maybe a good idea to do this together?