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.
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.
The code I used for WP should work with Jekyll. We were talking on twitter - a priority of mine for 0.7x is to revamp the blog comments plugin. So when I do that I'll also make sure it will work on Jekyll at least (haven't used the others so no promises there)
Thanks @psychobunny, I will do the beta-testing if it is done. Digging in ~
@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.
Hi @psychobunny and all,
any update on that jekyll compatibility? I tried the wp code to no avail. Could be operator error, for sure. I get the following error:
XMLHttpRequest cannot load http://bb.piccolboni.info/comments/get//2015/09/syntax-directed-diffs-for-R-in-R/0. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://piccolboni.info' is therefore not allowed access. The response had HTTP status code 404.
Origin here is where jekyll is running. Loaded resource is nodebb instance. Any suggestion appreciated.
I may be wrong but there are three codes, wp, ghost, and a generic code... have you tried the latter?
@julian Where can I find the generic code for using NodeBB as a commenting system? My blog is static, and I'm looking for a commenting system -- being able to use my current install of NodeBB would be great!