Closed sampottinger closed 11 years ago
More thoughts on this...
tracer_db_config.json acts as a whitelist for operations on the TRACER records database and (likely) will not change based on runtime environment and may (arguably) travel with the repo.
config.json acts more as environment configuration and will (arguably) not travel with the repo in the fullness of time. This would probably be a file that lives on the server and acts as a (slightly more secure / structured) alternative to reading environment variables.
So, I think we may want to keep them separate. Of course, we could have a discussion about the file vs environment vars.
This seems ok to close?
+1
With commit d6fa8e67a49ce921e2167fcc4f7663ee96469357, an second JSON configuration file was introduced. If the tracer_db_facade branch is accepted, a new subdirectory for configuration files should be added.