I confirm that I am not able to reproduce the issue anymore, thanks.

reputation requirement does not work for us since restricting 1 asshole affects 1000 regular users... We use signature/about me sections very actively, so people usually fill that information right after registering...

I think my "profile info scanner plugin" idea can solve all these issues :rofl:

profile info scanner plugin

Hi, Every now and then, some folks create an account for their +18 job... We are a family-friendly forum, which I believe is the same for everyone here. Of c...

favicon

NodeBB Community (community.nodebb.org)

Looks like I also misconfigured the proxy server, /assets was pointing to an empty directory (it used to work until i moved it forgetting it was mentioned there)

Hi, I switched from docker install to normal install and I wonder if i can automate updates because I will 100% forget to apply them in the long term

I tried to create a script to run once a month to do this:

delete everything except config.json, packages.json and uploads

get latest source for the 3.x branch from github

run ./nodebb upgrade as node user, then start it

but then I noticed that ./nodebb upgrade can ask "do you want to upgrade this plugin Y/N?", and so it can't be run attended in a script

I checked in the help and I did not see a command to make it unattended, so I resorted to just run it as ./nodebb upgrade -mib && ./nodebb start, which looks like it does not ask questions

What do you think?

@Gliding9426 Yes, they should... when you install a plugin via NodeBB, the package.json file is updated, and the plugin is downloaded to the node_modules/ folder, along with its dependencies. Both of those are on-disk, which is ephemeral on a Docker instance.

If package.json is updated to include the plugin, then when ./nodebb upgrade -i (or npm i, etc.) is run, the plugin will be installed alongside, automatically.

@Gliding9426 Yeah, NodeBB can fork itself and maintain its own state if you prefer not to use separate tooling. 👍