Heheh... no best practices as of yet, but that is the appeal of NodeBB. I (and I think the other admins and reps share our vision on this) really wanted NodeBB to be a "pick and choose" system to allow you to build a system you want to build, instead of what some other entity has decided.
I liken it to buying a computer. You could save time (and maybe money) by taking something off-the-shelf that a big box manufacturer as put together, or you could build the computer you want by picking the parts and assembling them together yourself.
As for best practices -- Node is really all about division of responsibility. Don't do things unless you absolutely have to do them, that sort of thing.
This is why:
Search is handled by Solr plugin
Avatars are handled by Gravatar
Emails are handled by Mandrill
Image uploads are handled by Imgur
I need some advice in connecting small sails.js app with nodeBB. In my sails.js application I need to get current logged user. I set sails.js session id key to express.sid (as in nodeBB), and configured it to use nodeBB collection as session storage. Then I can query for user id by session id (also from nodeBB storage). It is almost what I need to, but I can't get through some problems
nodebb and sails app have to be on same domain
when user visits sails app first, then nodeBB sets another session id and sessions are different on both apps
when user logs in nodeBB, gets new session id and also, sessions are different on both apps
Maybe OAuth is best way to go?
PS. Thanks for nodeBB, great work!