General Discussion

@Mega as @Schamper said, I only discovered this last week, so we use require.parent.parent/etc for everything, but require.main works just as well.

Keep in mind require.main's "scope" is app.js, so you'd have to do require.main.require('./src/groups.js'); if you want access to the groups lib.

require.main will always be app.js for plugins, since plugins are only called by NodeBB.

@birch said:

I had installed using the Installing NodeBB for Dummies.
...
the whole thing is a huge learning curve for me 🙂

It's perfectly fine to be learning as you go. It's one of the best ways to pick up experience, and interact with content to learn exactly what things do.

It appears as if you're using an outdated guide on @psychobunny's blog. While it is designed for installing at Digital Ocean, it was written for an old version of the platform, and it only installs using Ubuntu. f you're setting up an Ubuntu droplet, I must insist that you ignore everything written in the NodeBB for Dummies guide, and take a look at the specific installation instructions for installing NodeBB on Ubuntu.

While the guide does an excellent job of going in-depth, the OS-specific installation instructions are what you'll need to set up a new forum/droplet.

With that being said, there's a few tips for working with NodeBB as a beginner. When installing plugins or using npm from the command-line, you will lines that begin with WARN, as you have already noticed. These are usually harmless, and can often be ignored. However as you've since discovered when something says ERROR you've got a problem 😉

It looks like you've gotten some misinformation from your friend. There's no need to install PM2, or forever. Previously, there was a need as the NodeBB loader wouldn't restart the software if it went offline. With the recent versions (0.5.x or 0.6.x, I can't remember) NodeBB has the ability to restart itself when necessary. However, this doesn't mean it will detect an issue and attempt to correct it, it simply restarts NodeBB and the forum comes back up - unless there's a configuration error which prevents a component from functioning. It appears as if you've encountered this already.

When starting NodeBB, there's a few commands you can use.

./nodebb start Starts your forum in "production". If you go down, it'll restart itself. ./nodebb stop If NodeBB is running, this takes your forum offline. ./nodebb log This can only be ran after ./nodebb start. This shows what's going on in your terminal. ./nodebb dev Starts NodeBB in "development". This basically combines ./nodebb start and ./nodebb log. The forum only stays online as long as the dev command is operational. If you hit ctrl+c to end the console output, you also power off the forum. This is great for doing a quick test, and seeing what happens as you make changes. ./nodebb restart Restarts your forum. Pretty explanatory 😉 ./nodebb reset has a few uses. ./nodebb reset plugins Resets all plugins to their default settings ./nodebb reset plugin="nodebb-plugin-brokenplugin" Resets a single plguin to it's default setting ./nodebb reset widgets Resets widgets. Items are moved to the draft zone. (Not deleted, just disabled) ./nodebb reset themes Resets themes. Undoes alterations (I think - could be wrong on this) and reverts it to the original items. ./nodebb reset all Resets all of the above.

Now that you're familiar with these commands, working with NodeBB in the command-line should be a little simpler. In order to work with NodeBB using these commands, you will have to have navigated to the folder where you installed NodeBB.

I've noticed that you're trying to use a password with redis, but there's not a redis password required. In order to use a redis password, you need to edit your redis configuration to requirepass. You could do this through the terminal, but if you're new to working with a VPS I'd just recommend downloading the config through SFTP, editing it, reuploading it to overwrite the original file, and then restarting the redis-server service.

Let's have a quick chat about installing plugins. Since you're new to NodeBB, until we can get you up and running for at least one week straight, I'm going to have to ask that you do not install a plugin using npm install nodebb-plugin-pluginname or npm i nodebb-plugin-pluginname

You can install NodeBB plugins (and edit their configuration) in the Admin panel.

So for now, you've got an issue with nodebb-plugin-emailer-mandrill

As stated, you need to run ./nodebb reset nodebb-plugin-emailer-mandrilland then ./nodebb start

If you want to start fresh, I'm working on a blog post that's updated and may be able to help.

@Nguyen-Nga That particular problem is due to a query we want to run against socket.io being unavailable in the latest version. It presents when used in a clustering setup, and the latest changes to NodeBB always have clustering active (even in a cluster setup of 1 process), so in the meantime it is difficult to get the data in question. This is why those graphs are not working at the moment.

@Reik

Thanks for the tip. It seems to have converted the config to a different format (ie: instead of base_url it now uses url) and it's working. Seems odd that everything would fail all of a sudden without any changes.

@psychobunny @julian

Is there some kind of automatic update in v0.5 that is outside of normal nodebb operation?

@RazorAxis the only thing I can think of is that some CSS style aren't being recognized by Firefox and IE for whatever theme you're using. I wouldn't expect this to happen though, since we're using bootstrap.

Should make some more noise when you update an amazing piece of software such as NodeBB 👍

The sm-3 or 4 did not change the tablet in vertical but at least it now changes in horizontal. Gus that will have to do for now. Thank you for the help @yariplus

Darn, screwed that up huh.... Thanks @a_5mith 😛

@baris Much pending, I put some of my own cash in too though. 😆

Oh yeah just realized reading it again 😛 sorry

Check out this is you need better hosting 😄
https://community.nodebb.org/topic/3630/nodebb-hosting-option-for-people-interested

Very Good but HapHost is very very BAD.
NodeBB don't work.
128 Mb of RAM are to few.
Already installing plugins the site crash, because VPS arrives at the maximum of RAM.
OMG. Very Bad.

Without do NOTHING.
RAM : http://i.gyazo.com/2b0fcbb3c8a36dd3d0b40199393c59c3.png
CPU : http://i.gyazo.com/33656ee25ef23e9fec43dce06458caaa.png

FUCK.

@Schamper hi ! Have you found where this problem come from ?

I found a fix. It was an error in nodebb. When I did ./nodebb setup I made a typo in the port.. oops .-.

Anyway its all good now.

Hi,
I need some advice in connecting small sails.js app with nodeBB. In my sails.js application I need to get current logged user. I set sails.js session id key to express.sid (as in nodeBB), and configured it to use nodeBB collection as session storage. Then I can query for user id by session id (also from nodeBB storage). It is almost what I need to, but I can't get through some problems

nodebb and sails app have to be on same domain when user visits sails app first, then nodeBB sets another session id and sessions are different on both apps when user logs in nodeBB, gets new session id and also, sessions are different on both apps

Maybe OAuth is best way to go?
Thanks

PS. Thanks for nodeBB, great work!

The popup is a bootstrap modal.

@Technowix there are performance gains related to the new structures in ES6 (generators, async functions, classes, ect.) There also may be performance gains since they are updating the internal version of V8 to the latest stable version (Node is still on an older version from what I understand).

I'm learning something new here everyday! Muchas gracias Señor

Possible through session sharing... if the cookies both have the same secret...

In a nutshell, because database abstraction layers make compromises... 🙂