You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the database connection url as an alternative to the config file. Whenever I run a migration, gulp outputs some logs that expose the url. Is there a way to avoid this without the config file?
Example logs:
> com.***@1.0.0 migrate /Users/juanjo/development/web/backend
> sequelize --url postgres://$DB_USERNAME:$DB_PASSWORD@$DB_HOST/$DB_NAME db:migrate
Sequelize [Node: 0.12.0, CLI: 1.7.4, ORM: 3.6.0, pg: ^4.2.0]
Parsed url postgres://user:password@localhost/database *** <--- Hide this?
Using gulpfile ~/development/web/backend/node_modules/sequelize-cli/lib/gulpfile.js
Starting 'db:migrate'...
Finished 'db:migrate' after 75 ms
No migrations were executed, database schema was already up to date.
The text was updated successfully, but these errors were encountered:
I'm using the database connection url as an alternative to the config file. Whenever I run a migration, gulp outputs some logs that expose the url. Is there a way to avoid this without the config file?
Example logs:
The text was updated successfully, but these errors were encountered: