SOLVED: yii accounts duplicated on nodebb

NodeBB Development

Suggested Topics


  • 3 Votes
    6 Posts
    588 Views

    🤔 interesting...

  • 9 Votes
    10 Posts
    6k Views

    @pitaj said in NodeBB v1.6.0 has been released!:

    I suggest you try it. It has been tested with Gmail, but we haven't been able to test other providers there.

    The switch offers no explanation and seems not to do anything.

    The switch enables that configuration, but it only applies if an emailer plugin isn't activated.

    OK, thanks for the explanation.

    I think I will stick to the external SES plugin since, as far as I understand, this whole section is about using SMTP for sending e-mails which requires storing credentials in database. We use IAM roles to grant implicit permissions to use SES on instances that run our Forums - and nodebb-plugin-emailer-ses is able to pick that up.

  • 0 Votes
    2 Posts
    3k Views

    You'd probably have to write an SSO plugin to share authentication. @julian has a ton of SSO plugins that you could use as a sample in writing your own one 🙂

    julianlam - Repositories

    julianlam has 152 repositories available. Follow their code on GitHub.

    favicon

    GitHub (github.com)

    As far as user management... somebody was asking for a WP user management plugin. Kind of like if you upgrade a user's privileges in WP, it updates it in NodeBB as well. It's doable but the client didn't end up going for it so we never ended up building it

  • 0 Votes
    1 Posts
    755 Views

    I'll work in my research with 'late distribution'. This is a term adopted by me rs. It means that I need to split the code to work in multiple clouds. For example, the 'module' topics would be deployed in Amazon EC2 to use the load balance and the rest of nodebb code in GAE, implementing some communication between the code on the EC2 and GAE. Some ideas?

  • 1 Votes
    4 Posts
    2k Views

    To get back on this, I have currently solved it in the following way:
    ###/lib/nodebb.js:

    module.exports = { "Meta": module.parent.parent.require('./meta'), "User": module.parent.parent.require('./user'), "Plugins": module.parent.parent.require('./plugins'), "SocketIndex": module.parent.parent.require('./socket.io/index'), "ModulesSockets": module.parent.parent.require('./socket.io/modules'), "db": module.parent.parent.require('./database') }

    ###library.js:

    var NodeBB = require('./lib/nodebb');

    ###/lib/submoduleX.js:

    var NodeBB = module.require('./nodebb'), db = NodeBB.db, User = NodeBB.User, Plugins = NodeBB.Plugins;

    ##Why this works
    I read somewhere that require caches the files you load. That means that if require my nodebb.js from library.js, I can later load nodebb.js from any submodule I want and it will work.