4 ms·
> It's not straightforward. But it's no less straightforward than being your own CA in your dev environment and issuing a cert to any other name. There's no ne
by Spivak 10y ago
> It's not straightforward.
But it's no less straightforward than being your own CA in your dev environment and issuing a cert to any other name. There's no need to go through the hassle of getting a public cert for this use case.
- drvdevd 10y agoInteresting to note how important this is for developers to consider now. If we're going to move to an HTTPS only web, we need to both: 1) understand how CAs work (including how to be your own local CA) and 2) make this an easy or seamless process in terms of workflow. Granted, it's really not that difficult, but baking this into existing development environments will become a task many projects will need to repeat.
- voltagex_ 10y agoEven the "professional" development environments like Visual Studio aren't quite there. I've got a site at work that can only be run locally on one machine because VS won't issue the right certificate, and won't let me disable the SSL config.