config file in production about cli

[sdepold]

There was quite some related discussion here: #77

tldr is:

You can configure your configuration file to point an environment to a specific environment variable, which is supposed to contain a database URL:

{
  "production": {
    "use_env_variable": "DB_HOST"
  }
}

In that case the CLI will load the env var DB_HOST and throw it into the url module to parse it. Credentials can be passed as well.

[sdepold]

Would env vars be an options?

[marcoschicote]

Sure.

[marcoschicote]

Great. Thanks.

[benbonnet]

hope I'm not bothering coming by here; as for now this is not obvious

You then need to have two files to handle the configuration ( default sequelize.json, then some config.js than can parse environments variables) ? Or maybe 3 ( a something.js that declares which environments variables can be parsed via use_env_variable — according to #77) ?

As he is asking initially, wouldn't that be possible to handle the conf directly in index.js database/models definition file, using process.env vars, without relying on multiple external files ? This approach would sound a bit more straightforward and easy to understand