Added Dockerized MongoDb with Seed Data

[jasonwong26]

Closes #659
Closes #660

Summary

Added MongoDb container to docker environment.

Also added the new /mongo folder for storing the logic for generating seed data and loading it into the database. I have included a README.md within that folder with details on how to use it. But to summarize:

• The /data folder contains a set of JSON files that store the seed data.
• The /scripts folder contains a Node script that can be used to generate seed data using faker.
• The init.sh file contains the commands that are run when the docker environment is started to seed the database.

To retain the ability to run the project locally (without using Docker) I modified the backend/src/config/database.config.js file to recognize when it is being run within Docker via a new environment variable: DATABASE_HOST. When that is provided (it is included in the Docker-Compose file), the application connects to the Mongo database within the docker environment. Otherwise it uses the pre-existing DATABASE_URL environment variable to generate the connection string.

To fully illustrate this process, I have included a new Employee data model with an associated API endpoint: /api/employees/. Unrelated to the MongoDb changes, I used a different way of structuring the backend code. I'd like us to discuss whether this is worth wider adoption.

[drubgrubby]

Ran docker-compose build then docker-compose up

Got the following error:

We tried to run it locally with npm run start:local and got the same error

We went to the client folder and ran npm install, and then ran npm start:local again and it worked.

Still doesn't work with docker-compose up. Seems like we probably have to add sometime to docker-compose.yml or something. Working on it.

@jasonwong26 -> if you have a sec and know the answer, that would be great. Otherwise, we'll work it out. Thanks.

[jasonwong26]

Hi @drubgrubby,

Try deleting and recreating your docker containers - sounds like the docker environment is not pulling in the full list of modules.

[drubgrubby]

I tried deleting and re-creating the docker containers. Sadly, still getting the same errors.

I tried deleting the node_modules files and running docker-compose up, but that didn't work.
(The note_modules files were empty in the file structure after running docker-compose up, but I think that's proper).

I ran yarn install to recreate the node_module files just in case, but still nothing.

Putting this down for the moment.

[jasonwong26]

Hi David,

Try the following:

1. Delete all related docker images from your computer
2. Run the following script: docker-compose build --no-cache --force-rm && docker-compose up

I suspect the issue is that you need to fully rebuild the docker images. The docker-compose up command will reuse the cached image by default, running the build command with the no-cache flag should hopefully resolve the issue.

FYI - I added this command to the package.json file as part of PR #762.

Hope this helps!

[jbubar]

Got the same error

But.. I did look into this pr and I am super impressed Jason! Thanks so much for doing all this work

[trillium]

Closing this pull request as stale. If anyone disagrees feel free to reopen.