The or query for users was constructed entirely wrong
Finally got the or query straight for mongo (I hope)
Allow some skeleton directories to exist in the data directory for the sake of tests and runtime
[TRAVIS] Make extra certain that dependent directories exist before testing
Notes to self
No reason the centos Vagrant machine can't also host mongodb for test runs
Latest sane composer dependencies
Allow coverage to run with sane params
Properly query mongo with an 'or' query.  Refactored the or query into the user service where it belongs
Debug logging and error handling for product provisioning controller action
Should have gone with commit 95fa8232c193f98f1422cb5e24da760a16687d37
Solve once and for all how references are persisted into MongoDB and how they're hydrated out of MongoDB. Hashes, that is
Provisioning with RsApiProvisioner should be working if we can get the right JSON into it.  Still a work in progress