Oh hey, nice. Would anybody with Docker expertise like to review?

Yeah, I too don't have much of docker expertise, just went through circleCI docs, would love any review and/or resources to follow.
Looking through the code of main repo now, so that I can contribute to this awesome idea more.

Related issue: #281

@nveenjain can you add - build to workflows.everything.jobs at the bottom of the file? That'll add your new job to the list of jobs that get run.

I think that build got stuck in a loop. #259 might be the fix, if you get up to date with upstream master I think that'll work.

Ok thanks, will try that!!!

Looks like it is missing some environment variables, we could setup these environment variables in CI.
docker/compose#4189 (comment)
If they are already set, then docker/compose#4189 (comment) might fix.. I'll try the second one now...

The issue here, I think, is actually that the docker-compose file points to .env files in the services, but those are usually created manually by users based on the .env-example files. Adding in a step before docker-compose up that copies each of those would probably work.

I debugged this over on my own Circle and had some suggestions.

This looks good! Should definitely help prevent breaking the dev setup in the future.