Passing Flint and providing Developer Infrastructure

[penland365]

We need this project to pass Flint inspection, which it decidedly does not.

Building off @pengwynn 's first commit, I'm going to start by moving the script folder back to the top level. I need to create a handful of scripts to manage starting up the important components.

My preference for this is to rely on Docker to manage each module independently.

[penland365]

OK, I think I've got a decent path forward here. @pengwynn I'll give you a look tomorrow, but the gist of it is this:

• In the top /script folder, there is one basic script called 'check'. It checks for the only high level dependency, docker. If the we are on OS/x, it also checks for docker-machine. It does NOT download these dependencies, it merely tells you if they are on the path.
• Once the Docker checks are completed, it calls each sub-projects /script/check, i.e. api/script/check which checks the dependencies only needed for each project. This allows individuals to work on sub projects without having to potentially pull down the entire universe. For the API for example, all that is needed is a java 8 compiler and leiningen

As far as coordinating all the pieces together for a developmental environment, I'm working on small program that will be contained within this project called conductor. Conductor is a simple CLI program that does what it sounds like - coordinates any dependencies so that development in another module is simple.

For a front end project, a developer would simply run conductor -db v0.1.3 -api v0.2.0 backend. This would start up and run the db and api Docker containers, then stream the logs to the current window.

Thoughts?