Ah, not really... topic subscriptions are considered (in my opinion) user private data, and that is not shared by default.
You could instruct your users to adjust their settings if they are being notified about a specific topic too often:
@scottalanmiller Fluentd hosts some nice configs (distilled from a presentation from a Netflix engineer about tuning their servers) https://docs.fluentd.org/v1.0/articles/before-install
Perhaps this could help? Also check out ss -s, what is TIMEWAIT?
Hello, I'm wondering how I can make the teaser show subcategories within a main category. Currently it only shows the latest posts/replies from the main category and not what's inside of it:
Inside of it:
Is there a way around this? Thank you!
I filed a feature request recently, asking for hierarchical groups (for the full description see: https://github.com/NodeBB/NodeBB/issues/7410).
I completely understand this request may not help everyone, and perhaps its not considered something that should be added to the core.
To that end, does anyone have an idea how to efficiently implement the above in a plugin? I am trying to avoid multiple accesses to the DB, and obviously redundant c/p. How would you go about implementing that?
PostMidnight created this issue in NodeBB/NodeBB
Feature request: Hierarchical groups
Because of budget issues, I would like to install nodebb on shared hosting only. I have access to shell. I guess I can install if i have access to shell. Could you please say procedure as I can't find anywhere. Namecheap shared hosting uses cloudlinux OS and gives users to access shell
@MJ said in ./nodebb upgrade not works:
cd nodebb (or path to where nodebb is installed)
git checkout v1.12.x
git merge origin/v1.12.x
I have a "one liner" that I use like this. This is what I do...
git fetch && git checkout v1.12.x && git pull && ./nodebb stop && npm i && ./nodebb upgrade && npm i && ./nodebb start && ./nodebb log
I put the version right at the beginning so there is just one place to change it (a script and variable would be better, but I'm lazy.) I do the NPM install manually because it used to fail. Been using the same command since the 0.6.0 days, I'd guess. And I add the log at the end so that if I look away, I always see the log scrolling to know that things are okay.