ISSUE-27: Fix docker mongo setup

[carlan]

This is the fix for the mongodb initialization. I haven't tested on MacOS and Windows, it's working properly on *nix based OS's.

What was done:

• Updated server docker-compose.yml to add container name and new volume
• Updated main README.md to add a note on MONGO_HOST configuration
• Added mongo-init.sh to initialize mongodb container

Fixes #27 💚

Type of change

• Bug fix

PR Checklist:

• Merged the current development branch before submit a PR
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

[w3cj]

See comment.

[w3cj]

This is not required and happens by default... I removed all containers / images and db-data and was able to start up everything without this script.

The main fix that is needed is this:

• An init script on the API container that waits to see the message waiting for connections on port 27017 before starting itself.

[brilvio]

For the waiting connections I made a PR #39

[carlan]

The main fix that is needed is this:

• An init script on the API container that waits to see the message waiting for connections on port 27017 before starting itself.

See my last comment below.

[carlan]

👋 I had some time to work on this today.

I updated this PR to undo the changes I've made previously and introduce some new files to solve the issue. It's working fine on *nix. I'm curious to see it running on Mac.

One downside, the placeholder file docker-data/mongod.log will need to be present before hand otherwise docker will create it as a directory and we need it as a file. I had to update the gitignore and check in the docker-data and the placeholder file. EDIT: this isn't relevant with the latest changes.

Let me know your thoughts on it.

EDIT: I saw you had a bit of hard time understanding/remembering (no offence intended) what's going on. I should have added a comment explaining what I've done. Sorry about that.
The solution I've applied for this is rudimentar simple, I believe as you wanted/mentioned on previous stream. On db container I'm exporting the mongo logs in a volume, without it the server api wouldn't have a way to check if the database is ready or not based on the string. On server api container, I'm reading the log from the same volume and waiting for the string before continue.