./nodebb start works like a charm and I've never had a problem with it.

Hey there guys,

We are using NodeBB as our gaming forum @ GameLeap and so far we're loving it!
It consumes an OAuth endpoint to authenticate users from our main site and this is the only way for them to use the forum for now. Users must have an account on our website.

We basically offer many courses and each course has a set of videos.

We're looking to extend the functionalities of our main site and what we aim for is a comment section for each video of each course. Currently I will be able to do this using our main site's database but I was like hey, why not utilize the forum to achieve the same effect? A comment section underneath each video that creates a topic on the forum and each reply goes directly to the forum.

I researched about how I can achieve this and I came across the worpress/ghost comment plugin and the write-api that you guys offer.

My questions are:

1. Can it even be done?
2. Would you recommend that I do it? Are there any people who have successfully done it?

Sure thing. Navigate to your server config file (/etc/nginx/sites-availble/your_file) or wherever you keep it and add one more server block before your main server block.

Important: Don't use rewrite, as that's a common pitfall, as stated here

So with that said, to canonicalize your domain:

-www to no www:

server {
    server_name www.example.com
    return 301 $scheme://example.com$request_uri;
}

To canonicalize your IP:

server {
    server_name your:ip:address:here;
    return 301 $scheme://example.com$request_uri;
}

And then finally your main server block:

server {
    listen 80;
    server_name example.com;
    [...]
}

@markcarey I created an OAuth2 endpoint on my website from scratch and made NodeBB utilize it successfully. It was the first time I engaged in such an endeavour and it wasn't easy!
I followed the examples provided in the OAuth2orize plugin's github.

Besically all you have to do is swap out the local db they use and implement your db logic. Also use some sort of UID generator for client ids/secrets.

If you have that done and are able to successfully authorize with some tool, for example Postman or the Google OAuth Playground it should be pretty straightforward from there to setup the NodeBB SSO OAuth plugin to fit your website.

@Danny-McWilliams If you're speaking about the NodeBB setup to use the endpoint - it's extremely easy. However, the endpoint can be kinda tricky.

The flow for the plugin for the forum is:

1. You fork the plugin
2. You provide information about your OAauth/OAuth2 Endpoint in the plugin source file (library.js)
3. You tell the plugin exactly how to access the user data returned from the endpoint (which properties hold which values)
4. Test.

Right now I'm also working on creating an OAuth2 endpoint for my app to try and connect NodeBB with it. I will be glad if you share your progress, @frankfrankly!

@LordRelish said:

Hmm, there is no such option in mine, running NodeBB v0.7.0. Either you wrote your version wrong, or I have a ridiculously old version (which I downloaded like a week ago).

I completely misspelled the version. I meant 0.7.1!

It looks like this http://i.imgur.com/gmIhsND.png

Sure you can. Go to the Admin Control Panel (ACP) -> Manage -> Groups

From there you can click 'Edit' on any group you want to hide from being publicly displayed and check the 'Hidden' checkbox.

Note: I've joined NodeBB since 0.7.1 so on older version it could be different.

I've been trying to fix the plugin and sort of managed to get the ACP working correctly. I can see the sections array in the api response from the categories route. However I am quite new to NodeBB and NodeJS and I am not sure how to implement the template file of my theme to render the sections correctly. I am trying to achieve something like this as a look https://www.cryptofr.com/

Hahaha, great! Stalk much :goberserk:

Hey there, I thought that would be a reasonable place to bring my problem up

I Installed the plugin on 0.7.1 with **Persona **and everything went smoothly.

However, the view for the plugin in the ACP is completely broken and unusable.

Also, I get some drag event error (when dragging the sections on the right) in the console

I tried reinstalling the plugin and whatnot.

PP: Also, all categories on the front page disappeared and will only show up again when I deactivate the plugin.

Really cool, guys! Looking forward to what you'll come up with!

@BDHarrington7 There, I deleted the connect-mongo module to replicate the problem that I had.

@BDHarrington7 Thanks for your help, I managed to get it up and running yesterday. The problem turned out to be npm. For some reason it never completely downloaded all modules.

I managed to figure that out by running the nodebb app with nodemon. When I ran it I saw an error get thrown, which wasn't in the nodebb log.

Simply put, always check your npm modules! Dependencies go deep and sometimes may get messy.

Cheers,

Mitko

@leksar No errors in chrome's console. On firefox, it seems to occur randomly, but I sometimes get the following error
The connection to ws://127.0.0.1:4567/socket.io/?EIO=3&transport=websocket&sid=Dq0LcrxqbiI3dTIXAAAx was interrupted while the page was loading.

I checked the partials to make sure everything is there. It seems like the view cannot be rendered properly.
I even tried reinstalling the rendering engine module with no success.

I forgot to mention that the /register page gets rendered. It looks like this.

Hey there,

I just started playing around with NodeBB and so far I am impressed with how easy it is to set up.

However, even though I managed to follow the simple installation process and start NodeBB (using ./nodebb start), all I got was a blank home page.

I configured my installation to work with MongoDB. I thought that may be causing some weird issues so I tried with Redis too. The result was the same. I even tried installing it on Ubuntu 14.04, Windows 8.1 and even on a Vagrant box (ubuntu/trust64).

I am kinda confused. The installation seems to have went correctly, after all I can start the app.

Am I missing a theme or something, or am I just stupid and have missed something?

P.S. I followed the official documentation in order to install.