-
|
Based on current Flowise documentation, it seems like Flowise can only connect to a remote Postgres DB for managing configurations, chatflows, and credentials if and only if Postgres is accepting NON-SSL connections: It feels like we need some sort of additional environment variable like Plus, we also need some way to instruct Flowise to either ignore certificate validation OR trust the DB certificate somehow -- likely as additional environment variables. @HenryHengZJ , any thoughts about this? To be crystal clear, I'm not talking about using Postgres as a Vector DB store -- I'm just talking about Flowise using Postgres DB to store and manage chatflow settings. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
You currently can set the env var DATABASE_SSL=true to connect to a Postgres DB that requires SSL (I believe Postgres 15+ defaults to required). There's also a PR that allows additional options, including self signed certs with the cert as base64 as an env var and the full set of options allowed by the pg npm library (PGSSLMODE). |
Beta Was this translation helpful? Give feedback.
You currently can set the env var DATABASE_SSL=true to connect to a Postgres DB that requires SSL (I believe Postgres 15+ defaults to required).
There's also a PR that allows additional options, including self signed certs with the cert as base64 as an env var and the full set of options allowed by the pg npm library (PGSSLMODE).