Replies: 9 comments 2 replies
-
Just attempting to "sell" this feature.
|
Beta Was this translation helpful? Give feedback.
-
Seems worth exploring. |
Beta Was this translation helpful? Give feedback.
-
I've been manually swapping out some certs in the nginx config and it works great... except for a couple of Valet commands that rebuild those configs.. I'm happy to work on PR if its likely to go ahead. |
Beta Was this translation helpful? Give feedback.
-
@tobz-nz I took a look at this today for awhile, with a particular goal: My primary hope was to remove the need to have But if we don't use openssl to generate a CSR then it's much harder to identify certificates in the Keychain as being specific to Valet and needing "cleanup" if people don't use That doesn't mean mkcert couldn't be used. I suppose maybe we could identify some other way to do system cleanup. While Valet puts its CA in the valet config dir, I suppose if mkcert is generally installed then people can use it to create other non-valet certificates too, so maybe we don't need to even be "valet-specific". Just make sure whatever Valet needs is present when mkcert is called in case someone's run other mkcert commands that might confuse valet. |
Beta Was this translation helpful? Give feedback.
-
I'd welcome seeing a PR with what you come up with. |
Beta Was this translation helpful? Give feedback.
-
Cool - I'll look at implementing this when I have some time. 👍 |
Beta Was this translation helpful? Give feedback.
-
Or maybe smallstep/certificates |
Beta Was this translation helpful? Give feedback.
-
Smallstep seems little bit overkill don't you think? |
Beta Was this translation helpful? Give feedback.
-
I'm about 80% through implementing mkcert. |
Beta Was this translation helpful? Give feedback.
-
MKCERT is a simple tool for making locally-trusted development certificates.
Sounds pretty perfect for integration into Valet right?
Beta Was this translation helpful? Give feedback.
All reactions