"some kind of superior master ring"
the admins here stuck in the 2000's are really having a weird inferiority complex in terms of docker. Its not a master ring, its not a magic supertool, its just clever, modern technology. Its a way to maintain systems with MUCH less hassle than was needed before. not everyone needs to understand the details of installing a microservice if the person that understands BEST maintains the docker and updates frequently for security and functional updates. If running a nodeBB forum is your lifes purpose, i can understand you enjoy the full install and undertanding how everything works, to the last detail. if its just another web service you are runing among 20 others, you dont give too much of a damn, you just want it to be as easily maintainable and servicable as possible.
The religious war is started by the people hating dockers, the others just want to make their job as productive as possible.
BTW, lets see how quickly somebody gets up a server after a linux distribution change using traditional methods vs. a server thats dockerized 😉
In communities where we participated heavily, but didn't run the community ourselves, we used to build tooling that would go post by post and pull out some of this data and record date-time and poster of different posts and threads to track how people would post over time.
This could be for anyone, but for an admin specifically... we are posting some content that some people don't want notifications on. We know which content this is and would happily mark it as "don't notify" when posting to allow it to go into "unread" or whatever, but not to email anyone. Is there any way to do this? Or to suppress notifications for an entire category to basically do the same thing?
A little tooting of our own horn, but today is the fifth anniversary of the MangoLassi IT Pro Community which started in 2014 running on NodeBB since day one. Still growing after five years and a great partnership with NodeBB that has done so much to make it all possible for us.
It may also be possible to set up a script running client-side that would submit a post at a certain time, though that would require you keep your tab open (but would probably be better than the CLI method).
Making a little app that does it externally would only be so hard, too.
Has anyone done this type of stuff, either as a plugin or even as a stand alone app that simply hits the NodeBB data store (we use MongoDB, not Redis, so that matters if going that route)...
We'd like a way to get detailed user stats on a per user basis. Like how often, and it what categories, an individual is posting. We want to be able to research individual user patterns over time. Of course we can just query the DB, but this is something we'd like to see regularly both in ad hoc queries and in reports. Would be awesome to not reinvent the wheel if someone else is doing this, but I suspect no one else is. But wanted to ask before we look at making something ourselves.
Happened on the MangoLassi community. Appears to have happened in someone's chat session. The result didn't bring down the forum, but did break some things like quotes and replies and we could no longer find the end of threads. But mostly the forum was intact. A restart fixed everything, and we've never seen this bug before. But didn't want to fail to report it, either.
We are on NodeBB 1.10.2, all plugins fully up to date (and very few in general), and NodeJS 10.8.0.
2018-11-02T15:50:41.288Z  - error: /user/donahue/chats/2255
at nextTask (/opt/mangolassi-1.0/node_modules/async/dist/async.js:5324:14)
at next (/opt/mangolassi-1.0/node_modules/async/dist/async.js:5331:9)
at iteratorCallback (/opt/mangolassi-1.0/node_modules/async/dist/async.js:1064:13)
at Immediate._onImmediate (/opt/mangolassi-1.0/node_modules/async/dist/async.js:2799:21)
at runCallback (timers.js:694:11)
at tryOnImmediate (timers.js:664:5)
at processImmediate (timers.js:646:5)