@tqwhite Is it docker?

@tqwhite

My test

In short, I tested ubuntu 14.04 and mongodb 3.2 from clean install with

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927
echo "deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.2.list
sudo apt-get update
sudo apt-get install -y mongodb-org

And added next to /etc/mongod.conf

security:
  authorization: enabled

And every thing is perfectly working. Even more funny thing is that, if one remove above authorization: enabled part, then mongod doesn't care of a password, which means any arbitrary passwords include empty string works fine with nodebb and mongodb

Also mongod data filew are at /var/lib/mongodb. even I have no /data

Question

So I would like to ask how you installed mongodb. By compile?

Some Information.

Actually I installed mongodb 2.4 first and install mongodb 3.2 on it. And I found out /etc/mongodb.conf and /etc/init.d/mongod were not updated. This means, service mongod start will bring wrong configurations. One should do start mongod instead of service mongod start to use proper configurations via initctl

Congratulations!

By the way, can I know your OS version? I would like to test by myself also

@SimonQ said:

The email is still not being sent through... Am I missing anything else? (I'm using the test email option that @julianlam suggested)

Edit: I received it after a few minutes of typing this!

• Edit : I missed second line begins with "Edit", congratulations

Have you checked email logs at mailgun site? That is the first thing you have to see.
I always keep it opened while email testing

OK, now I think I got full stories

Actually, my first question to your situation is that

@tqwhite said:

When I type "mongod", it starts the Mongo daemon. After I do that, I can start and run nodebb with no problems at all. Works 100%.

You might mean that you executed mongod at /var/lib/mongodb ( usually that is the data directory ), don't you?

something like

cd /var/lib/mongodb
mongod

@tqwhite said:

I just can't figure out how to specify the equivalent of "auth=true" in YAML.

I think you already did this, but just for sure.

From https://docs.mongodb.org/manual/administration/configuration/

security:
   authorization: enabled

So now, I have questions to the NodeBB development team. @julian

1. About @frissdiegurke 's idea.

   • What do you think? Is it secure or do you have any better ideas, policies , plans?

2. To manage dependencies between plugin,

   • Can we enforce to install and activate plugins by dependencies?
   • Or can we give warnings of wrong configurations, dependencies and so on by plugin on admin UI ( dash board? )?

3. Do we have secure way to add/remove/modify custom data by plugin in a filtering pipe?

   • For example, on filtering hook, data.pluginData.<plugin name> can be always for plugins (means some sure for core will not use it for different reason!! ), whether they are removed or not after filtering. I know if I select good name( random or highly uniq), then it will be quite safe but it will be better if we have an official space.

4. If I want to make a npm module which is dedicated to NodeBB while it's not a plugin, then what is good name for. Maybe nodebb-helper-any-name. It may be for individual plugins.

I had one more, but I forgot what was it while writing....

It's outdated, so don't use it.

1. you can use just redis instead of nodebb/docker:ubuntu-redis and build nodebb image with Dockerfile of NodeBB ( from official github repo ), but only for testing purpose.
2. Or check mine ( NodeBB with Docker full chain ( nginx, redis, mongodb ) )

But here is genenal answers for your questions.

Basically If a container is alive ( means if you can see the container with docker ps ) then you connect to bash shell

docker exec -it <container name> bash

If a container is Exit status, then it's more complicate. here An Golden Rule is that any modifications in containers is temporary and you will loose it. ( even there are ways to save a current container to image, but it's worst idea ).

Basically you can't connect to a container in Exit status, but

1. You can copy from or to the container with docker copy
2. You can manage files if you mounted volumes
3. After you solved problem then you can docker restart. BUT remember the Golden Rule

So best idea is, I think, you have to be able to make your own Dockerfile with proper options from scratch( means from ubunt) or official docker image like redis.

Docker is fun and powerful, fantastic, good to study, but much more complicate than without it before you have enough knowledge and skills. And even it will harm you easily.

Nevertheless, I don't discourage you to use docker!!, I encourage it
I'm just giving a most important tip here. "Don't use docker for production before you know how to deal with a concept of a temporary container" but GOOD FOR TEST AND LEARN.

Welcome to docker

And always do back them up.

@charles one can make an import plugin, but an easiest and efficient way for (quick) testings will be just with redis data dump file. First, load redis with data file, and that's it.

However, I agree that the importer can be better at some point.