Try CTRL + X.

I love it, seriously. It makes the forum looks different, but inviting.

Short answer: I would use reverse-proxy as the solution.

The thing is, something.com is actually pointing to something.com:80, so if you want it to work without resorting to reverse-proxy solution, try to tinker a bit with the configuration file of the NodeBB so that your NodeBB uses port 80 instead of 4567. Else, install Nginx (or Apache2), and use it as reverse-proxy.

Hope this article can help you.

Edit: Here's the official documentation telling you how to do it, that reverse-proxy thingy.

The installation is no different than regular installation of NodeBB on any kind of Linux, IMHO. Maybe the first speedbump would be installing the NodeJS itself.

On Arch repository, the current version of NodeJS is v0.10.30, which is the latest version on the NodeJS website. So getting NodeJS on Arch would be as easy as pacman -S nodejs.

Next step would be getting a copy of NodeBB from the git, so you can start here

https://docs.nodebb.org/en/latest/installing/os/ubuntu.html

... and then just simply follow the rest of the guide.

That is my server block to serve NodeBB. During setup, I set the NodeBB's URL to 127.0.0.1 at port 4567.

server {
        listen   80;
        server_name forum.abc.me;

    location / {
         proxy_pass http://127.0.0.1:4567;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection 'upgrade';
         proxy_set_header Host $host;
         proxy_cache_bypass $http_upgrade;
  }
}

This server block is saved as nodebb.conf in /etc/sites-available, then symlinked to /etc/nginx/sites-enabled by running the command sudo ln -s /etc/sites-available/nodebb.conf /etc/nginx/sites-enabled/. Of course, run the sudo service nginx reload after that.

I can give you some tips.

1. I prefer to set up Nginx as the reverse-proxy so all the HTTPS/SSL stuffs I just throw them to the Nginx. Easier that way. Perhaps this docs can give you a kickstart on reverse-proxy thingy.

2. Self-signing your certificate is okay, but when other people browsing your forum they would be spooked by "certificate not trusted" warning. Here's how to get a free CA-signed certificate.

I guess that's all for now.

Hi fellow members of NodeBB. I am trying to do something new but common here, which is every 2 weeks I will write a short article on my blog about cool stuffs I found on the internet. The new thing here is that I am not going to write a laundry list of apps / softwares / tools / useful websites, but I am going to try my best to reflect my knowledge about that apps / softwares / tools / useful websites, and if it is possible I will also include the similar solutions to that apps / softwares / tools that I may have encountered before.

So here is my first attempt, Roundup Episode 1 on my blog. I am hoping you guys can participate at least here, by commenting tools of the similar kind that you may be using now or you guys had used in the past.

Sharing is definitely a sexy thing in this decade!

Awwhh the lord haz come to invite me. I don't know, because I don't really use NodeBB quite intensively as for now. Let's see how it goes. By the way, this is for you.

I just updated the roundup, and the episode 2 is available here on Faith.na. Couple things worth mentioning:

• Previously I posted the episode 1 on Defiance.NightlyArt.com, but then I moved that article to Faith.NightlyArt.com because Faith is my techblog for all long-form articles.
• There are 66 links of pure awesomeness, so do check it out!
• I hope this helps.

Have a great weekend!

@boorish yeah same concern here. The requirement to run Discourse is monstrous (1GB RAM minimum, while my Jekyll-based blog costs virtually nothing, just need a bit resource for the nginx). Right now I am running NodeBB on a 256 MB OVZ instance, so far it hasn't hit anywhere near 220 MB.

Good morning from US Northeastern region.

As you can see above, the user hexth has broken link to his avatar. Upon inspection, I found out that the account is registered via Twitter SSO. And upon a bit deeper inspection, it seems like he changed his avatar on Twitter.

My question here is: how to make sure the user avatar doesn't go blank like that, if the user registered his/her account via Twitter SSO?

Hi guys!

First and foremost, this new thread is a response to these threads:

1. How to Transfer data from Redis to MongoDB, oh hi @suraj
2. [OLD] Migrate NodeBB from MongoDB to Redis?

Short answer: Not really possible at the moment.

Long. Long-ish answer: It is possible by using the importer, which I guess you might need to wear helmet and kevlar before doing that, and a bunch of duct tapes. You might want to check it here: Database Migration. The other way to do this without using the nodebb-plugin-import is to deal directly with both database, which might be intimidating for beginners.

First, if you are currently using Redis, export/convert the dumped database .rdb file to JSON (which can't be done directly through the redis-cli, as far as I know), and then import that JSON file into the MongoDB. Follow the discussion here on GitHub: redis-cli ability to convert an RDB file into JSON or CSV and vice-versa.

For the brave soul, I recommend you guys to try. For the less brave soul, be braver.

Redis as the in memory key-value storage

If you fear that your Redis will fill up the maximum available capacity of the memory, use MongoDB. When you are in doubt whether or not the Redis will fill up the memory, use MongoDB. However, theoretically speaking, a VPS with 512 MB RAM will do fine. I don't have number here, but I believe the NodeBB core developers can tell about their current setup and how much the NodeBB + Redis consumes the memory.

However, if you are interested to over-engineer your NodeBB installation, try this advanced setup: NodeBB + Redis + MongoDB.

Extra Notes

Feel free to read my lab notebook when I was experimenting with the Redis maxmemory function: NodeBB - to Redis, or not to Redis, and also the afterthoughts here: when I was experimenting with Redis, I didn't backup the db

Hope this thread helps to clarify few things!

@Pakorn yes you are right. Just checked my NodeBB's config.json. I put http://forum.abc.com as the URL during the ./nodebb setup with the port 6379.

@Pakorn I don't think you need. The nginx code block that I posted above is what I've been using on my NodeBB and couple of Ghost blogs before. It is just the matter of redirecting the traffic.

That is my server block to serve NodeBB. During setup, I set the NodeBB's URL to 127.0.0.1 at port 4567.

server {
        listen   80;
        server_name forum.abc.me;

    location / {
         proxy_pass http://127.0.0.1:4567;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection 'upgrade';
         proxy_set_header Host $host;
         proxy_cache_bypass $http_upgrade;
  }
}

This server block is saved as nodebb.conf in /etc/sites-available, then symlinked to /etc/nginx/sites-enabled by running the command sudo ln -s /etc/sites-available/nodebb.conf /etc/nginx/sites-enabled/. Of course, run the sudo service nginx reload after that.

@boorish yeah same concern here. The requirement to run Discourse is monstrous (1GB RAM minimum, while my Jekyll-based blog costs virtually nothing, just need a bit resource for the nginx). Right now I am running NodeBB on a 256 MB OVZ instance, so far it hasn't hit anywhere near 220 MB.

Thanks @psychobunny, I will do the beta-testing if it is done. Digging in ~

Hi guys,

I am aware that NodeBB currently supports WordPress and Ghost for it to function as a commenting platform. Has anyone attempted to use the NodeBB's comment system on static content generators like Jekyll, Nanoc, and Octopress? I have few blogs running on Jekyll, and I am kinda interested to use it as the commenting system instead of relying on Disqus.

Thanks guys.

p.s: Found someone using the Discourse as the commenting system for his Jekyll blog

This is pretty much a very quick feedback after browsing this forum with the NEW theme (capslock'ed because I like this new look).

1. Need better font styling for the quote (and spoiler too), maybe? I noticed the bigger font size. Sorry no suggestion for code (I am in hurry).
2. Might need lightbox to display the picture embedded in the thread, if I am not alone feeling that opening the image on a new tab after clicking that image feels tad bit annoying.

All in all, I truly like this theme. Sexier, and it looks like candies to my eyes.

I just updated the roundup, and the episode 2 is available here on Faith.na. Couple things worth mentioning:

• Previously I posted the episode 1 on Defiance.NightlyArt.com, but then I moved that article to Faith.NightlyArt.com because Faith is my techblog for all long-form articles.
• There are 66 links of pure awesomeness, so do check it out!
• I hope this helps.

Have a great weekend!