greenmoss
commented
6 years ago We have two options:
- Load in the db configuration at runtime. That already has a json file. Another way to do it would be with environment variables.
- Alternately, we could "cheat" and hard code the db configuration. Since we're part of a pre-defined Docker cluster, we could get away with that.
I'm starting to lean toward the second way, since it gets us going faster. What do you think?
Created directory for the DB Configurations. Wanted to initialize it just the same as what was done for the sql scripts. But then I got confused with this: "We want the db_config_travis.json file to be copied via a volume."
Also tried running docker using the method defined in the wiki. Got problems when it comes to docker-compose down savant.
Still searching how to add the json using volumes.