Reading config from committed .js files is going to make managing many deployments difficult
Closed this issue · 3 comments
Environment configuration is currently handled by adding / modifying Javascript files in the app/scripts/config
directory. As we're adding multiple DAACs with multiple environments each, that's going to become a problem to manage, and is going to make deployments more challenging. It would be easier if that configuration were read in from a JSON file. If that were the case then our deployments can just populate the config with the correct values before building.
sure. that's totally possible. we can do both json or yml. We can also add switches in forms of env variables. Do you have a sample in mind?
I would expect it would have the same structure as the objects exported by config.js
. So something like:
{
environment: 'development',
apiRoot: 'https://cumulus.ds.io/api/lpdaac/',
graphicsPath: '/graphics/'
}
moved to jira at https://bugs.earthdata.nasa.gov/browse/CUMULUS-120