Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #117
Description:
Running tests now (on dev wsl):
global.setup.js
, which checks if all containers are healthy, if they are not healthy in 60s, it fails and tests don't runnginx
andfrontend
health checks pass with just a response,backend
now has a dedicated/api/health
endpoint which checks eachbackend
component - if one of them is down, it returns503
instead of200
Changes made:
e4f5b24 modifies backend dev dockerfile to use caching speeds up build times by 6x
9ddd701 adds
/api/health
endpoint which checksWebsocket
andStore
readinessdcbe06d adds timeouts to flaky game board hiding test
944a58e adds docker health check to
docker-compose-dev-wsl.yaml
88d5e3c adds
global.setup.js
to wait for containers healthy status before running testsNote:
I have only made changes to
docker-compose-dev-wsl.yaml
since I can't make sure if the regulardocker-compose-dev.yaml
works after I modify it. I'm hoping @joshzcold you can add it and verify that it works on your machine.Although there is a go health checks library, I felt this was not needed here, but I copied the response format from their example