JSON the right format for config? about cli

[leehankyeol]

For anyone who might be lost like me...

If you're using dotenv, you should require it in config.js.

const dotenv = require('dotenv').config();

module.exports = {
  development: {
    database: process.env.DB_NAME,
    username: process.env.DB_USERNAME,
    password: process.env.DB_PASSWORD,
    host: process.env.DB_HOST,
    port: process.env.DB_PORT,
    dialect: 'mysql',
    define: {
      underscored: true
    },
  },
}

[mcranston18]

For anyone wondering why sequelize -c my_config.js doesn't work, the syntax has been updated. Use this instead sequelize --config my_config.js

[sdepold]

Yeah that would work as well, you only have to tell the CLI to use the js file as configuration file:

sequelize -c my_config.js

[sdepold]

Hi @anthonator,

there is this thing called use_env_variable... You can find it here:

cli/lib/tasks/db.js

Line 191 in ff71914

if (key === "use_env_variable") {

If I get that right, and please let me know if that is the truth, because we should add that to the docs then, you can do this in your config.json:

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

Having that you can set an env var DB_HOST to the URL of your database. Not entirely sure how that url looks like though. Please let me know if this helps already. Otherwise I will try to find out one is supposed to use that :D

[Nastromo]

Current version of sequelize-cli supports config.JS by default. All you have to do is write your config.js as this:

require('dotenv').config();

module.exports = {
    dev: {
        username: process.env.DB_USER,
        password: process.env.DB_PASS,
        database: process.env.DB_NAME,
        host: process.env.DB_HOST,
        dialect: 'mysql'
    },
    "production": {
        "username": process.env.DB_USER,
        "password": process.env.DB_PASS,
        "database": process.env.DB_NAME,
        "host": process.env.DB_HOST,
        "dialect": "mysql"
    }
}

Note - your "dev" parameter name in config.js has to be exactly the same as in your .env file

[anthonator]

Thanks for the reply @sdepold! I haven't had a chance to try your suggestion yet, but it seems like a rather round about solution when you can write native JavaScript to handle this scenario easily.

module.exports = {
  production: {
    database: process.env.PG_DATABASE,
    host: process.env.PG_HOST,
    dialect: 'postgres'
    ...snip...
  }
};

Is there any reason the above wouldn't work? Could simplify the config code (no JSON parsing!).

[anthonator]

Perfect! Thanks @sdepold! This might be handy in the docs if it's not already there.

[frederikhors]

Is this still a problem or am I wrong? #688

[noodlebreak]

There is no config.js in my installation. Is this to be manually written? I have an automatically created models/index.js when I ran sequelie init.