Build a crash prediction modeling application that leverages multiple data sources to generate a set of dynamic predictions we can use to identify potential trouble spots and direct timely safety interventions.
Basically whenever a commit is pushed to a branch on the main repo, it will trigger a build of an image that is tagged with that branch name (the exception being master branch which relates to the image tagged latest)
We can enable/disable this for any branch as necessary, but right now it's probably fine to have all branches enabled.
I've created a PR that updates the documentation around the Docker aspect of the project, as well as clearing up a bunch of old references to boston-crash-model
@bpben @j-t-t @alicefeng @shreyapandit I got my access to the D4D Docker Hub account elevated and we now have automated builds running on all branches - https://hub.docker.com/r/datafordemocracy/crash-model/tags/
Basically whenever a commit is pushed to a branch on the main repo, it will trigger a build of an image that is tagged with that branch name (the exception being master branch which relates to the image tagged latest)
We can enable/disable this for any branch as necessary, but right now it's probably fine to have all branches enabled.
Thanks.