Technical Support

@rbeer That did the trick, thanks a bunch!

Thx for the quick reply 👍

Kobold

Thanks @SimonQ! I'm sure that will be very helpful 🙂

@julian This may sound silly but, if I were to place the dump.rdb file back into /var/lib/redis (from my NodeBB install) and reset my server from there would anything horrible go wrong?

You're looking at an older version of Majestic. It's very outdated now, but you can purchase newer versions on the forum.
v4: https://community.nodebb.org/topic/3279/majestic-4-5-final
v5: https://community.nodebb.org/topic/4017/majestic-5

@sonia @baris we should launch shouldn't we... :trollface:

After 0.7.0 I think we wanted to launch weekly or something

i decidede to fork the recent cards plugin, and modify it to have the html markup i want only on the category page.

Moved to: https://community.nodebb.org/topic/5998/nodebb-plugin-teamspeak-0-5-to-0-7

Sorry for your time. Was too forgetful to check server logs. It's my mistake, I didn't deactivate the nodebb-plugin-ns-slugify which made for 0.7.1 version, not for 0.7.0. 😐

@psychobunny thanks!

Thanks @baris that did the trick

@julian That's very stupid of me....i was thinking the time in Canada is 5 hours later then here but i have been mistaken with the time in Indonesia Where my daughter spent her trip. In Indonesia it's 5 hours later then Europe [Netherlands] My apologies for my mistake

It is taking me some time - mostly because I'm not familiar enough with NodeJS / NodeBB.

Some observations:

Took a while to get the ./nodebb setup routine to work - had to do it first for MongoDB and then for Redis and then combine the two files and restart (redis / mongodb nodejs files do not get installed on the npm install command).

Then got stuck with launching multiple processes on reboot with systemd. Gave up on that and just used a crontab @ reboot line to run a shell script. Need to figure out how to restart / reload processes seamlessly.

Found some issues with socket.io and spdy - did not investigate, disabled spdy on nginx.

Found some issues with the 0.7.0 branch and upgraded to master 0.7.1 and found that much more stable. But these were plugin related - sections, adsense - dropped them both.

Made the mistake of setting the production flag in the environment variable NODE_ENV. 🙂

As of now, have a test site running persona, notifications plugins on a distributed setup - NFS / REDIS / MONGO DB on one server and a barebones NODEJS + NGINX/SSL on another.

Seems stable for now on a test setup on https://devlib.org will give it a day or two while I play around with the templates / plugins and watch memory usage, before I go through another effort to set the autoscale / loadbalancer up.

@baris @julian @psychobunny - I really like what I see so far. Well done. If all goes well with the setup / eval, I will be dropping you guys an email to see if I can fund some development. 🙂

Instead of using ajaxify.variables.get('topic_name') now you can access the data returned on a particular api route by doing ajaxify.data.title. The old meth...

NodeBB Community (community.nodebb.org)

You don't have to worry about it if you are not developing plugins.

Im running ubuntu, i created my own startup (init.d) script so it loads on boot

You'll want to listen to the hook I mentioned above, and make a call to groups.isMember() to check group membership status, and then save it to the corresponding users' information.

For 1 I would be inclined to use clustering then reverse proxy the subdomains to categories. Rather than spooling individual instances for each. I've done this at my own site.

dnb.35hz.co.uk will take you to the electronic category.

You could then make a few changes to how your homepage/main website looks and do it that way.

As an additional. Anything you're not sure exists, drop an email to sales [at]nodebb.org and they may be able to create what you need.

@psychobunny @julian
A special user/group for the ACP would be nice to have, though.

I am thinking in terms of: Intrusion starts with spotting the user with desired credentials. This way administrator/moderator/team accounts couldn't be targets to any attacks. As such a username (account with ACP access) wouldn't be exposed to the public, whatsoever.

But since many BBs, for many years did well without it, I come around to the first line: "Nice to have". 🙂

If you're on latest core, you also need to install and activate the nodebb-plugin-composer-default plugin for topic posting to work

It's still not working. I enabled it like you said. Previously , when it wasn't working for one of my users , that was when all the plugins were all enabled too.

edit: I renabled all plugins except for the lavender theme , and it seems to be working now - tested it on IE and chrome.

I think the lavender theme has some code that's conflicting with the composer , since it got updated recently.