I decided to give the checker its own Dockerfile because it builds a different binary and could have different dependencies. We could build two binaries in the existing Dockerfile but it seemed more consistent with the Docker philosophy to have a single-application image.
This can run daily scans with a checker/docker-compose.yml like
Depends on #206
I decided to give the checker its own Dockerfile because it builds a different binary and could have different dependencies. We could build two binaries in the existing Dockerfile but it seemed more consistent with the Docker philosophy to have a single-application image.
This can run daily scans with a
checker/docker-compose.yml
likeand a
checker/shared/check.cron
likeI'd like to commit those to a deploy repo managed by techops.