how to manage data for existing users who did not give consent? We had to remove all of their post?
In my case there are many users that aren't active anymore but wrote a lot of interesting messages. Removing their post would be disastrous.
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
There are two main reasons why this guide has been published. I have had to limit mobile bandwidth consumption on 3G connection and to get rid of Git and Ruby issues. Mixing them up with Windows command line is a bit quirky.
Linux and other *nix users should skip it and go with your official guide. I have tested it on a local computer with Fedora 21 Server and it is really easy to reproduce. But on Windows it is not.
And you do not need to change so many firewall settings for cmd.exe, ssh.exe and similar processes. Using web-based OpenShift tools is also much easier for beginners.
This is the community forum of the forum software named NodeBB. It is not a forum for general Node.js questions. Though they are, of course, allowed, you'll have better luck on StackOverflow or elsewhere.