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 have multiple environments, and for lower environments I run the migrations using the config.json file. However, for Production I don't want to list the credentials in the file, nor do I want to have to set them up as env variables because there are multiple people working on the project and that means that all have to set them.
I would like to run migrations using the --url parameter
ERROR: connection is insecure (try using 'sslmode=require')
I tried using ssl=require, sslMode=require, sslmode=true, not providing it at all, etc. However, I'm using this exact same connection string to connect the app to the DB, and it works fine. No matter what I do it doesn't seem to take the sslmode param into consideration. Any suggestions?
The text was updated successfully, but these errors were encountered:
Sequelize CLI [Node: 20.18.0, CLI: 6.6.2, ORM: 6.37.4]
I have multiple environments, and for lower environments I run the migrations using the
config.json
file. However, for Production I don't want to list the credentials in the file, nor do I want to have to set them up as env variables because there are multiple people working on the project and that means that all have to set them.I would like to run migrations using the
--url
parameterUsing Postgres, stored on Neon.js. Running
npx sequelize-cli db:migrate --url "postgresql://{{username}}:{{password}}@{{host_url}}/{{db_name}}?sslmode=require"
is throwing an error
ERROR: connection is insecure (try using 'sslmode=require')
I tried using
ssl=require
,sslMode=require
,sslmode=true
, not providing it at all, etc.However, I'm using this exact same connection string to connect the app to the DB, and it works fine. No matter what I do it doesn't seem to take the
sslmode
param into consideration. Any suggestions?The text was updated successfully, but these errors were encountered: