Right now I am building a VM on Koding to get NodeBB up and running...
Thanks to NodeBB, I now have accounts on Heroku, Openshift and Koding

Re: Support for Sass based themes

Seeing that Bootstrap 4 is based on Sass, I guess that you will be moving from Less to Sass for themes soon, right?

@julian said:

Yes, you can do this with the blog-comments plugin. Instructions are in that plugin's readme.

Are you talking about the same plugin? The psychobunny plugin?
Or is there another generic comments plugin elsewhere?
Because this one is for Wordpress and Ghost ..
Or, do you mean that the instructions for Ghost will work for everything?

@Pixel I am sure that we don't want new ways to educate people. There are enough already.
I am referring to the Yii Framework forum and the Ogre3D forum - not exactly small communities.
Where people are already sending PMs because they want you to debug their code, or give them an answer.
I don't think that behaviour should be encouraged.
And adding the option to flag your own post is exactly that.

It is Christmas already!

In my opinion, allowing this would be a major weakness in itself.
Unless I misunderstood what you're saying @sanatisharif - you want to be able to take a topic with no replies and add it as a post to an existing topic?
Why not just let the lonely topic be, and die of age on it's own?
Or at least lock it, either automatically by means of a plugin/setting (old topics goes out of date) - it just feels wrong somehow

Thanks a lot @julian

I threw in an if(found) just in case - but I am always amazed by how little code is required.
That seem to happen a lot with Node.js and a well written software entitled NodeBB

@Pixel I am sure that we don't want new ways to educate people. There are enough already.
I am referring to the Yii Framework forum and the Ogre3D forum - not exactly small communities.
Where people are already sending PMs because they want you to debug their code, or give them an answer.
I don't think that behaviour should be encouraged.
And adding the option to flag your own post is exactly that.

In my experience, people will abuse that option to get moderators to answer their question. I already seen it happen too many times elsewhere.
If nothing else, it is a sure-fire way of pissing off over-worked moderators, and could even get you banned

@MJ I haven't tested it yet because my installation works and I don't feel like reinstalling just yet
However, from what I've read, doing a git hard reset is what 'you should do', apparently.
My problem was that I thought I could perform a ./nodebb upgrade on an install that I did from a downloaded archive. You need to have checked it out from git. (I reckon).

I've got internal error so our problems might not be related - except Mongo.
They recently switched to Mongo and still have lots of Redis related stuff in the code..

Search does not work on my installation either.
I guess it has got to do with Mongo.
It worked with Redis.

In my opinion, allowing this would be a major weakness in itself.
Unless I misunderstood what you're saying @sanatisharif - you want to be able to take a topic with no replies and add it as a post to an existing topic?
Why not just let the lonely topic be, and die of age on it's own?
Or at least lock it, either automatically by means of a plugin/setting (old topics goes out of date) - it just feels wrong somehow

I have installed NodeBB in every permutation of what is written in the docs, and have failed numerous times.

So, checking out master and performing a reset actually makes ./nodebb upgrade work?
I must try this at home ..

I threw in an if(found) just in case - but I am always amazed by how little code is required.
That seem to happen a lot with Node.js and a well written software entitled NodeBB

Thanks a lot @julian

It works

(function(module) {
    "use strict";

    var autoreplyit = {};

    autoreplyit.filter = function(data, callback) {
        var re = /http:\/\/nodebbjacmoe-jacmoe\.rhcloud\.com\/topic\/(\d+)/;
        var str = data.plaintext;
        var found = str.match(re);
        data.subject = data.subject + ' #' + found[1];
        callback(null, data);
    };

    module.exports = autoreplyit;
}(module));

Totally hard-coded, of course

Edit:
I am fully aware that it is only a matter of time before a kind soul points out to me that I can easily get the site url from a dark corner of the API - but, hey: it works.
Now the receiving PHP script can grab the topic id and make sure that it is sent to the right place.