NodeBB Offline help

NodeBB Development

Suggested Topics

  • 5 Votes
    6 Posts

    If you are going to store a lot of stuff I would use ./src/cacheCreate to create my own, ./src/cache is for a few stuff that never changes like the list of categories etc. If you put a lot of your own stuff in there like urls for link-previews it will negatively effect the performance. For stuff like that just create your own lru cache.

  • 0 Votes
    4 Posts

    More specifically, the issue is that it defines a static directory in plugin.json:

    "staticDirs": { "s3": "public" },

    But doesn't have it.

    It seems to be an artifact of people forking and updating it without fully understanding what exactly it was doing - looking back at some history at some point someone moved the templates from public/templates to just templates/ and apparently NodeBB wasn't enforcing that directories have to exist at that point, so it wasn't noticed and all future forks inherited this bug.

    NodeBB is IMO doing fine here - a lack of directory a plugin declared to have might suggest some issue with the installation or the plugin itself (for example a typo in a path). A plugin incorrectly declaring something it doesn't use can't really be distinguished from these issues.

    Also, @julian while .gitignore works, I feel like it's a bit of abuse of that feature and the name is misleading (upon seeing a directory with .gitignore my first thought would be that something is supposed to go there but will be ignored. And I feel without knowing much about git I might've assumed it meant the whole directory would be ignored by git - the opposite of what it actually does). I personally prefer the convention of using an empty file named .gitkeep (or just .keep), since it more obviously refers to keeping the directory and wouldn't have any other potential impact on files included by git.

    EDIT: TL;DR of the issue:
    why would nodebb do this

  • 6 Votes
    1 Posts

    We've released v1.15.4. Check out our GitHub page for fixed issues:

    Release v1.15.4 · NodeBB/NodeBB

    Node.js based forum software built for the modern web - Release v1.15.4 · NodeBB/NodeBB


    GitHub (

  • 0 Votes
    2 Posts

    Found a "hidden" file in the nginx/sites-available and nginx/site-enabled folders.
    Deleted that and now I only have one nginx warning left.

    When running 'sudo nginx -t' this is the result:
    nginx: [warn] conflicting server name "" on, ignored
    nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    nginx: configuration file /etc/nginx/nginx.conf test is successful


    Ok i have now also removed the return 301 (line 4) in the nginx server block, I think it also conflicts with the rewrite in line 5.

    Restarted server/nginx/nodebb
    And boom HTTPS works.

    Next thing though, we still don't get to see a greenlock in firefox or chrome. It says something about the site only being partially secure. Any idea why that happens?
    Now also fixed, our logo was still referring to a http link, removed the domain and just made it point to src="/assets/uploads/system/site-logo.png"

    PS. any other tips or adjustments on the config files is also welcome 😉

  • 0 Votes
    2 Posts

    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.


    GitHub (

    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