Category Notification is even better than what i tried to do, thanks for that. I know there is the Chat function but i was imagining something like a "Reply with PM" function in the Reply dropdown, guess that does not exist or is there a plugin for that as well?

We are trying to establish a forum for a group of freelancers in a large Company. One of the Goals is to enable us to offer and reply to "Swap Shift Offers". We want people to be notified when a new offer is posted, the only way i found is to make a Category "Swap Shifts", within that a single Post and the offers have to be posted as a reply to that post. If you want to be notified you can turn on the notification for this thread.

What i couldnt figure out yet: If you want to replay to an offer, is there a way to send a private message to the Person that offered the shift, instead of discussing it in that thread, triggering notifications to everyone again?

Alternatively it would be great if one could follow an entire Category and get a notification when a new Post is made in that Category, but thats not possible or is it?

Cheers,
e.

Forget it buddy. I think your reading skills a flawed. As i said before i dont have problems with my containers. The official NodeBB docker container does not adhere to essential docker rules, which are: do not mess with persistant data. But i doubt you are able to grasp that. Lets leave it here.

@gotwf

wow
"some kind of superior master ring"
the admins here stuck in the 2000's are really having a weird inferiority complex in terms of docker. Its not a master ring, its not a magic supertool, its just clever, modern technology. Its a way to maintain systems with MUCH less hassle than was needed before. not everyone needs to understand the details of installing a microservice if the person that understands BEST maintains the docker and updates frequently for security and functional updates. If running a nodeBB forum is your lifes purpose, i can understand you enjoy the full install and undertanding how everything works, to the last detail. if its just another web service you are runing among 20 others, you dont give too much of a damn, you just want it to be as easily maintainable and servicable as possible.
The religious war is started by the people hating dockers, the others just want to make their job as productive as possible.

BTW, lets see how quickly somebody gets up a server after a linux distribution change using traditional methods vs. a server thats dockerized

I really dont get what your problem is. I can do this for myself or i could help the person responsible for the NodeBB docker to make a proper container for everyone. One that doesnt overwrite persistent data. If i was the maintainer, the choice would be clear. So, what IS your problem, are you the maintainer and dont know how to make a proper docker container but too proud to let someone help you ;)?

You are weird.

@Per0x I am using Redis as well and like i mentioned, it is no problem to restore the db, if you KNOW its going to be overwritten on a docker pull. But since this is something a properly made docker would NEVER do, i didnt take the precaution of backing it up. Now i do. In any case, its just not good style to overwrite things in persistant directories, it completely contradicts how docker logic works and besides, its very easy to do properly, there are literally THOUSANDS of example Dockerfiles to see how its done. So my question is who maintains the official docker image so to maybe help make a properly configured image.

I can't believe you guys are having this discussion in 2019. You do realize that virtualization and containerization have become a standard tool nowadays, right? A lot of you sound if you got stuck somewhere in 2010 technology.

So, who made the Dockerfile of the official Docker image and did he/she implement some kind of upgrade check?

@Per0x Yup, I know & I have a volume for the redis database. That's not the problem. The point is that after doing a "docker pull" the nodebb installation does not check if it's already configured and has a database, but starts the web installer, which overwrites the existing database at some point. At least that's what I guess is happening. Did you try it yourself or are you talking about how it should work in theory, because I tried several times... Obviously you can backup your DB before updating, but a "docker pull" should not result in triggering the web installer - if the instance is already configured. And if it triggers the web installer, it should never overwrite an existing database.

I would assume (haven't checked yet), that the docker Image does not check if there is a config-file and database after a "docker pull" in which case it should run an upgrade and not the initial installation routine.

Maybe to clarify: typically you don't update any docker Microservice by using the softwares built in update mechanisms, but you just pull a new docker file with the most recent version, which then should be aware of any prior existing config and database and run any necessary upgrades but NOT act like a fresh installation.

Actually i signed up here just to discuss this issue. There is not only no documentation on the "official" nodebb docker, it is impossible to see who maintains it.

also, the docker image is not persistent, doing a docker pull overwrites the database, which is pretty much unacceptable, so there is some work that needs to be done. i would be willing to chime in here with my limited knowsledge of both docker and nodebb but i think it would be good to know first who maintains the docker...