Skip to content

Conversation

@ai-Ev1lC0rP
Copy link

…DATABASE_SSL parameter. The changes allow for more flexible SSL configurations to be passed as a JSON string through the DATABASE_SSL environment variable.

Changes made:

Modified the getDatabaseSSLFromEnv function in packages/server/src/DataSource.ts to parse the DATABASE_SSL environment variable as a JSON string. Added support for complex SSL configurations, including the ability to specify a 'ca' certificate file path. Maintained backwards compatibility with the existing DATABASE_SSL_KEY_BASE64 and boolean DATABASE_SSL configurations. To use the new functionality:

Set the DATABASE_SSL environment variable to a JSON string containing the desired SSL configuration. For example: {rejectUnauthorized: true, ca: /path/to/certificate.pem} This change allows for more granular control over SSL settings when deploying to Azure, while maintaining compatibility with existing configurations.

Cason Clark and others added 2 commits October 15, 2024 14:10
…DATABASE_SSL parameter. The changes allow for more flexible SSL configurations to be passed as a JSON string through the DATABASE_SSL environment variable.

Changes made:

Modified the getDatabaseSSLFromEnv function in packages/server/src/DataSource.ts to parse the DATABASE_SSL environment variable as a JSON string.
Added support for complex SSL configurations, including the ability to specify a 'ca' certificate file path.
Maintained backwards compatibility with the existing DATABASE_SSL_KEY_BASE64 and boolean DATABASE_SSL configurations.
To use the new functionality:

Set the DATABASE_SSL environment variable to a JSON string containing the desired SSL configuration.
For example: {rejectUnauthorized: true, ca: /path/to/certificate.pem}
This change allows for more granular control over SSL settings when deploying to Azure, while maintaining compatibility with existing configurations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant