Setup connection options for SQL Server #319
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
markmetcalfe
force-pushed
the
mssql-connection-encryption
branch
from
f039ab9 to
bdee391
Compare
markmetcalfe
requested review from
markmetcalfe
and removed request for
markmetcalfe
markmetcalfe
approved these changes
Mar 31, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The SQL Server images used in docker-dev are configured with self-issued SSL certificates. These aren't secure so the driver/library will reject connections unless you force it to trust the certificate.
Most developers will use the included SQL Server images, so it makes sense to include that configuration in the default config.php