Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Doc PR: fastn-stack/fastn.com#470
When connecting to PostgreSQL we currently support 1. unencrypted connection, and 2. verified certificate.
Heroku does not allow unencrypted connection, and the certificate they issue is self signed (I think), so can not be verified.
To support Heroku PostgreSQL we have added
FASTN_PG_DANGER_ALLOW_UNVERIFIED_CERTIFICATE
. If this environment variable is present, set totrue
, unverified certificate would be be accepted.Using this environment variable is a bad idea and right certificate should be used in production using
FASTN_PG_CERTIFICATE
environment variable.