Yes, indeed, if you're looking to scale up to handle high concurrent user loads, scaling out horizontally is your best bet. We've got a client right now serving 700+ connections at the moment, and they're on four separate NodeBB instances. It's probably too much for what they need, but it's always nice to have more capacity than needed in case of spikes, etc.
NodeBB on top coder
-
Thanks for the quick response, may have more questions later.
Shannon
-
Can i subscribe or watch this thread so it emails me any new posts?
-
Not yet, in the meantime, you can follow the post by clicking on the ...
... oh, I guess you can't follow posts on this theme... @psychobunny ?
-
@julian said:
Not yet, in the meantime, you can follow the post by clicking on the ...
... oh, I guess you can't follow posts on this theme... @psychobunny ?
@mashannon168
When clicking on the heart of the first post there's a "Watch" option. -
@Mr_Waffle said:
When clicking on the heart of the first post there's a "Watch" option.
D'oh! Thanks for that @Mr_Waffle
-
Thanks, now a follow up question, can i reply from the email?
-
@mashannon168 said:
Thanks, now a follow up question, can i reply from the email?
As far as I know, you get no email notifications -- yet! You get a notification about replies when you open the site though.
Theoretically email notifications can be build as a plugin. Would be better in core imo though. -
^ I agree, core, and fire hooks for the
nodebb-plugin-emailer-*
just like registration, password reset, etc.But about replies? that gets a little tricky, each "plugin" would either have to poll from it's service provider, not sure if that's possible on all, then theoretically,
Topic.reply
to the target topic. -
@bentael said:
^ I agree, core, and fire hooks for the
nodebb-plugin-emailer-*
just like registration, password reset, etc.But about replies? that gets a little tricky, each "plugin" would either have to poll from it's service provider, not sure if that's possible on all, then theoretically,
Topic.reply
to the target topic.Looks like there's a
ThreadTools.getFollowers
available though. Insert tid, get uids back -
let the spamming begin !
-
Do you support windows? I tried to setup node on windows, but I got some path issue in some plugin. I solved this issue, by coping some files from one folder to other. Application was working correct yesterday for me, but I get this error today:
D:\topcoder\tc_node_bb\poc\nodebb\src\logger.js:41
Logger.setup_one('loggerPath', meta.config.loggerPath);
^
TypeError: Cannot read property 'loggerPath' of undefined
at Object.Logger.setup (D:\topcoder\tc_node_bb\poc\nodebb\src\logger.js:41:45)
at Object.Logger.init (D:\topcoder\tc_node_bb\poc\nodebb\src\logger.js:36:10)
at async.series.async.parallel.db.getObjectFields.themeId (D:\topcoder\tc_node_bb\poc\nodebb\src\webserver.js:171:12)
at D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:551:21
at D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:227:13
at iterate (D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:134:13)
at async.eachSeries (D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:150:9)
at _asyncMap (D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:226:9)
at Object.mapSeries (D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:216:23)
at Object.async.series (D:\topcoder\tc_node_bb\poc\nodebb\node_modules\async\lib\async.js:549:19)Any idea?
edit
I forgot to run redis. Anyway this error is not meaningful.
The first error is
Error: ENOENT, no such file or directory 'd:\topcoder\tc_node_bb\poc\nodebb\node_modules\nodebb-plugin-mentions\static\plugins\nodebb-plugin-mentions\autofill.js'
but the real path is D:\topcoder\tc_node_bb\poc\nodebb\node_modules\nodebb-plugin-mentions\static\autofill.js
-
I had a similar issue when i installed it on windows. All i did was copy the files from the actual path into the one NodeBB wants. Had no problems since then but it might be worth raising an issue on Github.
I had to create
\static\plugins\nodebb-plugin-mentions\
and copy everything from
nodebb\node_modules\nodebb-plugin-mentions\static\
into there. I can get the exact files for you when I get home, if you want?
-
Yes, I did that and it worked. Anyway someone should fixed it
-
Weird... I'm on Windows and I'm not getting that.
-
Anyway someone should fixed it
(chuckle)
That style of script injection doesn't seem ideal anyhow -- may refactor it so that they can be defined straight in
plugin.json
-
@Mr_Waffle I think this was in a fresh install with a
npm install
It happened when i deleted nodebb and re-installed it.
-
How to create custom icon in alternative login?
Currently there is something like this in css files
content: "\f082"; }``` Could someone explain how it works or provide some link?
-
Another question.
in plugin I have settings something like
meta.config['social:auth0:app_id']
How to output settings to js in client side? I solved this by making custom route, which returns JSON with settings, in client side I make Ajax call. Settings are static and how to do it without ajax? -
-
@julian I did my own oauth plugin, I have button, menu, route etc, but I would like to have some different icon in alternative login list
For example how to define my own css class.fa-topcoder-square:before { content: "\f082"; }
What is that \f082 here? How can I define new values?Also my second question is not answered. Facebook, google oauth don't pass appId or other settings to client .js directly, but my plugin must do it. Is there some proper way to do that?