[nodebb-plugin-forms] Request for feedback

General Discussion

Suggested Topics


  • 1 Votes
    1 Posts
    174 Views

    I'll soon be creating a custom theme and some plugins for a forum that is already in use and I'm thinking about running second instance on beta.forum.url with the new theme and plugins enabled when it's close to being ready (but in need of testing), that I'd like to work with the same database as the main forum - so that users can just use beta if they want to preview new features while still using the same forum as others.

    Now, I know that the list of themes/plugins enabled is stored in database, so I'd probably need to do something about that, but is there anything else that would stop me from running two instances with a bit different configs off one database? Some sync issue with posts/topics or something like that?

    EDIT: actually, since I might as well help others, would it be a good idea to add an option to add some instance identifier to db plugin entries to core? Perhaps in config.json? So that if it's set NodeBB would look for plugins:<instance>:active for example.

  • 0 Votes
    1 Posts
    661 Views

    I have an instance of nodebb running in a subfolder of another site that is served via https. I can view the forum site without any problems but cannot view or install plugins (its possible I cant do other things but this is the obvious problem at this point).

    The error I get is the following:

    Error parsing plugins : Hostname/IP doesn't match certificate's altnames: "Host: packages.nodebb.org. is not in the cert's altnames: DNS:[domain].com, DNS:www.[domain].com.

    How can I overcome this problem?

  • 0 Votes
    3 Posts
    1k Views

    I have plans on fixing this, but I had alot todo. But you can use my packages nginx + nodejs + mongodb if you want

    Here is my repo: https://github.com/Jenkler/docker

    Check it out

  • 0 Votes
    1 Posts
    795 Views

    I just did an install of NodeBB 0.8.2 and it installed nodebb-plugin-emailer-mandrill 0.3.1 with it which is only compatible with NodeBB 0.9.^. In addition to the declared version problem I was also getting a socket.io/helpers related error on NodeBB startup until I removed the mandrill plugin.

    I worked around this problem by removing mandrill and then installing it like this:

    npm install [email protected]

    I poked around to see how nodebb installs nodebb-plugin-emailer-mandrill and it appears that this plugin is installed in a special way? It is not mentioned in the package.json requirements for nodebb.

  • 0 Votes
    10 Posts
    4k Views

    That looks good to me. Although I am not sure if it would have any side effects to other routes without testing can't tell for sure. I only see one db call in there for themes. I am not sure if there could be a case where webserver.js is required from app.js and then webserver.init is called before all the setup is done in webserver.js.