Docker compose for dev

[Benjamintdk]

Resolves #12. Builds on #23 #24 #26 #27. This PR aims to incorporate a docker compose file for development. Additionally, while not within the scope of the branch name, a Github Action was implemented for running tests as well, as there were some changes made to the test docker compose file along the way, especially with regard to the networking aspect.

Major changes:

• Docker compose file for development

Miscellaneous changes:

• Github Action to automatically run tests with docker compose test

Actions required:

• Add secret AWS_ACCESS_KEY_ID to OrcaAL repository secrets
• Add secret AWS_SECRET_ACCESS_KEY to OrcaAL repository secrets

[valentina-s]

@Benjamintdk I have been trying to spin up the app through docker-compose (on Mac). The ML and API endpoints start well and I can access them through localhost:5000 and localhost:5001 (and getting the statistics from the browser works). However, I get an error and trying to get the statistics:

Is there something I should configure regarding the networks?

[Benjamintdk]

@valentina-s I have provided a stack trace of the api service docker container below. If you wait for a while, you should see something along the lines of this, which indicates that the service is now up and running:

The error thrown is because the api service tries to send a get request to the statistics endpoint but the ml_endpoint has yet to finish training and predicting, and hence the statistics are not yet ready. To remedy this, I used a health check within the docker compose file to periodically check for when the ml_endpoint service is stable before starting up any other services. The ideal fix would be to add in the error handling for that part of the code to ensure the service does not fail while waiting, or to add in an await/async block to wait for the ml_endpoint to return the result. However, I felt that that was beyond the scope for this PR as I did not want to make too much refactoring to the code base itself, and hence left it as it is.

[valentina-s]

@Benjamintdk After fiddling with the number of retries in the healthcheck, I can get through the api working and returning 200. However, after that I get an webpack-dev-server error:

I tried npm install webpack-dev-server -g as some forums suggested but I was not sure at which step of the set up to do it.

[valentina-s]

docker-compose.test.yml -> docker-compose.test.backend.yml docker-compose.test.frontend.yml