Ok, before I start, many of this may probably also could have made it into a github issue. But actually this is more intended to have a dialog that may some read here that wouldn't do on github.
So lets start on this topic:
While NodeBB has really evolved in the last year, I have seen really positive development though, I nevertheless stopped using it.
My Reasons to stop using NodeBB
The reasons for this are quite simple, handling upgrades and scaling NodeBB was not yet stable. I can't say if it is now, but I suspect it is not.
So why do I suspect that?
Well simply, I have tested it now for a few weeks again and after the first patch has been released, it was the 0.9.1 patch and I tested today again with the 0.9.3 patch, it ran quite straightforward right into the wall.
Something is broken right now, to be exact: It is the upgrade script. It seems to do something clever, it deletes a dependency it needs next to migrate the schema and throws this error
21/12 20:30  - error: Unable to initialize Redis! Is Redis installed? Error :Cannot find module 'connect-redis'
Well while this is easy to fix, this is the first example, why I still think NodeBB is not yet ready for a real world production environment.
Zero downtime and docker
The next points are docker and zero downtime deployments. Zero downtime deployments are only possible, if the Software allows to really zero downtime deploy it. That means that data store or database migrations are zero downtime safe, e.g. they do not delete anything the Software needed before the upgrade, but possibly when the whole upgrade is done. And who screams zero downtime deployments needs also to scream even louder zero downtime rollbacks. The same rules, just for the other direction.
What really helps while scaling and deploying is docker, thus it is questionable: Will there be a maintained dockerfile? Will there be maintained heroku build scripts? Or even maintained builds in the docker registry? I know that for the latter one there have been docker container, but it seems like they have been shut down again.
So here are the final questions, where is NodeBB going and can we expect the upgrade process to be more reliable than it is yet? Reliable in terms of automatization?
And also what are your thoughts about this, zero downtime, docker and the future of NodeBB in general?
I'm eager to listen to your minds..