[0.6.x] Add config option to utilise Valet TLS certificates #129
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.
This PR introduces a new
valetTls
configuration option to allow developers to use Valet generated certificates on their Mac. This is useful as Vite 3 no longer generates a self signed certificate. Valet also puts certificates into the system keychain, so if you are using Chromium or Safari the experience is seamless.Unfortunately Firefox does not seem to read from the system keychain, so you may still need to additionally accept the Valet certificate for the Vite server, as we currently have to.
When setting the configuration option to
true
, the plugin will automatically detect the host by checking the current directory name and appending the configured Valet TLD:If you have linked you site via a different host, that is if you are in the
my-app
directory and ran:so that you can view "my-app" by visiting https://my-host.test, then you should specify the host along with the TLD in the
valetTls
option:User config will always take precedence over the underlying generated Valet config.
Documentation PR: laravel/docs#8164