dev/core#1926 - Try to autodetect mysql ssl settings from the CMS config #18264
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.
Overview
This goes along with #18107 but isn't required by it. It just tries to autodetect if ssl is already used for mysql on the CMS side and prefill the parameters for use with civicrm-setup. This PR does require #18107 if you want to r-run the whole process, but you can sanity check this one on its own without running the whole process by:
cv core:install --debug-model --cms-base-url=http://site/
and look at the output. In the simplest case with no client certificate and no server verification but wanting ssl it will look something like:Before
--db
parameter forcv core:install
to specify ssl settings.After
--db
parameter. You can still specify it manually if it guesses wrong.Technical Details
Autodetect is only for drupalish sites at the moment (drupal 7/8, backdrop).
Comments
Has test