Heroku - NodeBB Documentation

@pitaj @sharonyue should it be git checkout v1.8.x?

@baris This means now calls with the Bearer token can also be done to normal api?

@foyangyu curl -H "Authorization: Bearer fba206bd-8f0d-491e-83a9-b08383a4c575" --data "title='NEW topic TITLE'&content='CONTENT MORE THAN 8'&cid=4" http://localhost:4567/api/v1/topics how fully i am

Does it sit there forever? If so it's most likely an issue with the threads being killed. You can try setting "series": true in your config.json or you can try adding more swap memory to your system.

@brophy No i havent tried yet but this plugin have diffrent tags. Its a problem for my old posts.

@david_liuwx Take a look at loader.js

Hello, I have a forum hosted on AWS. The code is synced to master. I am using nginx on the same server, with SSL. Furthermore I am using Redis (provided by AWS). As of today's noon, when I browse the forum's address, I get ERR_TOO_MANY_REDIRECTS on the client side. Looking at the server logs I see "Error: misconfigured csrf". Let me assure you that the config file was not changed. Furthermore Redis is up and running (I can browse the database via Redis desktop manager). I tried resolving it till now (removing all plugins, removing nginx, removing FW, removing SSL, etc. etc.). In addition I changed the config file to: Website Hosting - Mysite.com https... www.mysite.com (the original value). 127.0.0.1:4567 (nginx forwards to that address) Nada... Its frustrating... Any idea ? Thank you in advance! JJ.

@paopevil said in Ghost cms with Nodebb in one VPS: but Discourse and Nodebb are better source code so you? Maybe you mean a comparison. I can give my personal view: Both are excellent, and the two best known next-generation forum applications. Discourse is a Ruby on Rails app, while NodeBB is a Node.js app. Discourse has more bells and whistles, while NodeBB is a bit simpler and more lightweight but with all the necessary features and more without being heavy on the servers. Discourse needs more server resources, while NodeBB is faster and more performant with less resources needed. In my humble opinion, Discourse's famous leader is very interesting and brilliant but very opinionated and can say repeatedly no to some user's frequent requests (e.g. over two category levels, pagination, etc.), while NodeBB's people are also very talented but more flexible trying to give options to the users. At the end of the day, both applications are really good and innovative, probably the best options for communities today.

I think I can do an use case scenario: A side permanent chat, so when you navigate the site, the chat remains there and only the content gets updated, while the chat is still available and you can still chat. More or less like the navigation-bar / nodebb-skeleton than when you change topic/category/pages it doesn't get reloaded.

This section is for entering category IDs like below. This will make any future topics posted to these categories automatically featured. You cannot feature an existing topic from this page. (most likely something I will add in the future) To feature an existing topic right now, you have to go to the Topic Tools of that topic:

@giggiux Thanks for the offer! At the moment no, I'm mostly fixing my ugly code and updating function signatures.

@paopevil I tried that and it added some strange code to my registration page. Doesn't look like it can be easily customized either. Does anyone have some sort of tutorial on how to use it?

When you run NodeBB in a cloud that has a load-balancer, reverse proxy, routers etc., it has to be configured to work properly, especially when you scale the server to use multiple instances. One of the constraints Socket.io, SockJS and similar libraries have is that they need to continuously talk to the same instance of the server. They work perfectly well when there is only 1 instance of the server Found this post too https://community.nodebb.org/topic/4383/hundreds-of-polling-requests That pretty much explains the issue i'm encountering on Cloud Foundry. Suspect it will apply to AWS too ...

Hello, just wondered if you could quickly point me in the right direction. I'm using the autoassigncategory plugin, however I would like it to auto remove the find/read permissions for newly created categories for guests and registered-public, do you know how I could do this or point me to the correct documentation? Thanks.

@giggiux I want to store the configuration/settings into SCM so that in the worst case scenario we can rebuild the instance. And i don't want to clone the datasets either

Thank you very much! @Giggiux