Sequelize Init Generator

sequelize-cli expects one configuration block per environment, and if you only run sequelize init once a year the shape slips away: which keys are snake_case, where DATABASE_URL belongs in production, what actually differs between development and test. This page hands you that skeleton with all three blocks written out and pointed at a local Postgres.

There are no inputs. The text is fixed, it renders as soon as the page opens, and the button simply reprints it. Look at how the environments differ: development and test spell out username, password, database and host, while production uses use_env_variable with 'DATABASE_URL', telling Sequelize to read the whole connection string from that variable instead of separate fields.

One thing trips people up: the content is module.exports, so it has to be a .js file, and sequelize-cli looks for config/config.json by default. Either add a .sequelizerc pointing at config/config.js or pass --config on the command line. The dialect is hardcoded to postgres, so edit all three blocks for MySQL or SQLite. Managed databases usually need dialectOptions with ssl too. It is all assembled client side.