Randy Fay
Randy Fay
`mkcert -h` shows you how to create a cert with many domain names, including wildcards. > $ mkcert example.com myapp.dev localhost 127.0.0.1 ::1 Generate "example.com+4.pem" and "example.com+4-key.pem". Just list all...
No, you can't create certs without knowing the names of the domains you're creating the certs for. I maintain [ddev](https://github.com/drud/ddev) though, that does all this for you on the fly...
These instructions should work for you, courtesy of @gilbertsoft: https://ddev.readthedocs.io/en/stable/#windows-and-firefox-mkcert-install-additional-instructions
I'm not @FiloSottile but please submit the PR, as long as you've confirmed it works on all platforms, mac (both architectures), Windows, Linux (arm64/amd64). It would be great not to...
Yeah, if you can't solve it on all platforms it won't be a go IMO. Ubuntu arm64 has certutil.... If you're copying the certutil binary from somewhere for each platform...
Not everybody uses package manager to install mkcert, although I note that it's now in Ubuntu 22.04 packages, not sure how it got there.
It seems that mkcert is also now in Ubuntu 22.04 and upcoming Debian 12 Bookworm, but it's not in Ubuntu 20.04 or Debian 11 Bullseye.
@cheslijones that's mkcert being unable to reaad the CA that's in *your own home directory*. You need to change the permissions on that directory (AppData\Local\mkcert, or consider deleting the whole...
There's an easier way to do this, without copying. See steps 4 and 5 in https://ddev.readthedocs.io/en/stable/#installation-or-upgrade-windows-wsl2