For a large part this is an architectural issue.
It would extremely useful if it were possible to test a plugin on the production database in a development or staging environment.
That's not possible when NodeBB gets the list of activated modules from the database.
We have a similar problem like this with Drupal7. It's close to impossible to test something on the production data without making a copy (which is extremely unpractical with a large DB) because of the tight coupling between configuration and content.
Haven't used it yet but Drupal 8 has improved on that issue quite a bit:
Managing your site's configuration
@xCausxn I am going to try out what you have said. But, I also wanted to know if this will work for Social logins on my website?
The users on my website can use Facebook, Google+ or local login to register to the website and use it. Now if I create the oauth system on my server, will it also be able to handle FB logins?
Sorry, I am pretty new to all this and still am figuring things out. Even if you can point me to the right direction, I'd be grateful.