Antonio Obregón

**Workaround** My application runs inside PM2 and the environment variables are injected from the **ecosystem.config.js** configuration file After creating the **.env** file with the environment variables, the **sequelize-cli db:migrate** command...

I think `sequelize-cli` runs outside of the PM2 environment and that's why it doesn't read the injected variables. When I have implemented `CI` it will carry out the process of...

I hope you're doing well. I wanted to check if you were able to find a solution or any workaround for this problem. I'm currently facing a similar situation and...

Note that the configuration file **_.sequelizerc_** uses **commonjs**, if possible change your project to **commonjs** I had problems executing migrations using ESM. Can you add error message and trace?

Your sequelize-cli configuration file **`config/config.js`** should have this structure: ```javascript module.exports = { development: { username: process.env.DB_USERNAME, password: process.env.DB_PASSWORD, database: process.env.DB_DATABASE, host: process.env.DB_HOST, port: process.env.DB_PORT, dialect: 'postgres', }, test: {...

There are two configurations, one for your app to listen to requests and another to execute the sequelize-cli commands