@priapo, @Master-Antonio is on my machine. I will change the python version for his account to 2.7.

@baris I deleted a thread in this category when my board was on 0.5.4... Now we're on 0.6.0-dev and the problem persists. DB backend is Redis.

@a_5mith I installed NodeBB following the docs exactly. That worked as described. I set it up, installed plugins... No problem at all. I didn't change any file by hand.

When it comes to upgrades, I just simply follow the docs and it always says that I have to commit the changes before. I guess the plugins may have changed something... I don't know.

Hey there!

NodeBB is a great piece of software, but it has a few things that bug me a lot. One of them being the upgrade process. I'm currently on the v0.5.x branch and I have to say: Not a single upgrade worked as described in the docs.

NodeBB’s upgrade path is designed so that upgrading between versions is straightforward.

This is clearly not the case. As mentioned above, I wasn't able to get a single upgrade working, because of friggin' git. I already said a couple times that I'm a dev myself, but I never really used git. I just scratched the surface of it, so if problems like "unresolved merge conflicts" or other exceptions (cough - yes, "exceptions") occur, I just don't know how to deal with them.

Okay, there are things like Google or this forum, but I just want to update and not ask for assistance any time I want to install the newest code. I always ended up downloading the release package from GitHub and replacing old files with new ones manually. That works most of the time, even though I'm not sure if I'm really on 0.5.4 now or not. I replaced the files as usually, but it still says: "Hey, 0.5.4 is out, you should update."

~ Another thing is the plugin system. Plugins are great and the way to install and update them is indeed straightforward. I noticed there were a couple plugin updates available for my installation and I updated all of them right away ending up in a broken installation. Had to reset all plugins. No matter which of them I enable now, I will end up in a "NodeBB is spinning up another process ..." loop.

Guys, I don't know how you manage your stuff and I really love your project, but you should really consider changing the way how upgrades work.

~ NH

I really love this plugin! But to be honest, I was fooled by the screenshot in the OP.
It would be great if we could pull topics from a specified forum category as blog posts and see topic posts as blog comments.

I'm still offering free NodeBB hosting right here! Drawback: No SSH access right now, so this might only be suited for absolute beginners.

@Master-Antonio Ahh alright. I'm fine with the current NodeBB permission system.

@Master-Antonio Could you please stop mentioning me? I'm hosting NodeBB for you, yes. But I'm not part of your issues with NodeBB. Thank you.

@baris Thank you so much for your help. I'm running 3 instances of redis now and it seems to be working.

@baris Okay, then I'll do that. Is there a way to easily dump and restore a single database from a redis instance?

@baris That's correct.

Yes, the chat messages are actually delivered on other instances. After reload, the chat messages are not displayed any more.

This is @Master-Antonio 's forum with a chat between him and me. He has UID #1 and I got #3.

This is my forum where I got UID #1 and it seems as I'm chatting with myself.

@baris Sure thing!

Instance 1

{
"base_url": "https://hanasu.me",
"port": "2339",
"secret": "such_secret (I changed this)",
"bind_address": "0.0.0.0",
"database": "redis",
"secondary_database": "none",
"redis": {
    "host": "127.0.0.1",
    "port": "6379",
    "password": "very password",
    "database": "0"
},
"bcrypt_rounds": 12,
"upload_path": "/public/uploads",
"use_port": false,
"relative_path": ""
}

Instance 2

{
"base_url": "http://unser-schleswig.de",
"port": "2340",
"secret": "very_secret (changed again)",
"bind_address": "0.0.0.0",
"database": "redis",
"redis": {
    "host": "127.0.0.1",
    "port": "6379",
    "password": "wow",
    "database": "1"
},
"bcrypt_rounds": 12,
"upload_path": "/public/uploads",
"use_port": false,
"relative_path": ""
}

Instance 3

{
"base_url": "http://37.59.31.162",
"port": "4567",
"secret": "do I have to do that again?",
"bind_address": "0.0.0.0",
"database": "redis",
"redis": {
    "host": "127.0.0.1",
    "port": "6379",
    "password": "-",
    "database": "2"
},
"bcrypt_rounds": 12,
"upload_path": "/public/uploads",
"use_port": true,
"relative_path": ""
}

Never touched the config after installation. Just followed the docs and thats it.

Hey, guys!

I'm currently facing very weird behaviour when hosting multiple instances of NodeBB. My setup is as follows, I'm running Arch Linux:

• 1 account to host NodeBB under
• 3 folders for 3 different NodeBB installations
• 3 different Redis databases
• 3 different ports used
• 3 different "secrets" used

Now, when I send a chat message to a friend, it will also appear on all other hosted forums. Same with notifications. What the heck happened here?

~Netto

Is this theme compatible with 0.5.2?

@Master-Antonio I still offer free NodeBB hosting right here: https://community.nodebb.org/topic/2291/offering-a-couple-nodebb-instances-for-free/11

I would love an one click upgrade solution which doesn't use git in the background. git works flawlessly most of the time but in case something isn't right, it might take unexperienced users a lot of time to fix it (like me, even though I'm a developer, I never really used git).

@babaggeii IMHO, fail-safe is more important than SEO. But maybe you could implement an option whether to use IDs or category names.

@babaggeii But what if you rename the category? Would possibly break the URL and lead to 404.

We're a mature Minecraft community from Germany and started using NodeBB ~2 months ago.
https://hanasu.me

I'm also using NodeBB for another project (community website for the city I'm living in). But I'm not done with that yet.
http://unser-schleswig.de