mkcert VS ddev

The experimental HTTPS flag relies on mkcert, designed for a single development system. If you run a Docker container, the flag won’t configure your local browser to trust its certificate.

The author mentions difficulties with HTTPS and trying stuff locally.

I've had some success with mkcert [1] to easily create certificates trusted by browsers, I can suggest to look into this. You are your own root CA, I think it can work without an internet connection.

[1] https://github.com/FiloSottile/mkcert/

Solution: mkcert – Your Zero-Configuration HTTPS Enabler Meet mkcert, a user-friendly, zero-configuration tool designed for creating locally-trusted development certificates. Find it on its GitHub page and follow the instructions tailored for your operating system. For Mac users employing Homebrew, simply execute the following commands in your terminal:

Well, Certifi does not ship with your company's certificates! So requesting internal services may come with additional painful extra steps! Also for a local development environment that uses mkcert for example!

My project, getlocalcert.net[1] may be the one you're thinking of.

Since I'm also building in this space, I'll give my perspective. Local certificate generation is complicated. If you spend the time, you can figure it out, but it's begging for a simpler solution. You can use tools like mkcert[2] for anything that's local to your machine. However, if you're already using ACME in production, maybe you'd prefer to use ACME locally? I think that's what Anchor offers, a unified approach.

There's a couple references in the Anchor blog about solving the distribution problem by building better tooling[3]. I'm eager to learn more, that's a tough nut to crack. My theory for getlocalcert is that the distribution problem is too difficult (for me) to solve, so I layer the tool on top of Let's Encrypt certificates instead. The end result for both tools is a trusted TLS certificate issued via ACME automation.

1. https://news.ycombinator.com/item?id=36674224

2. https://github.com/FiloSottile/mkcert

3. https://blog.anchor.dev/the-acme-gap-introducing-anchor-part...

Looks like step-ca/step-cli [1] and mkcert [2] have been mentioned. Another related tool is XCA [3] - a gui tool to manage CAs and server/client TLS certificates. It takes off some of the tedium in using openssl cli directly. It also stores the certs and keys in an encrypted database. It doesn't solve the problem of getting the root CA certificate into the system store or of hosting the revocation list. I use XCA to create and store the root CA. Intermediate CAs signed with it are passed to other issuers like vault and step-issuer.

[1] https://smallstep.com/docs/step-ca/

[2] https://github.com/FiloSottile/mkcert

[3] https://hohnstaedt.de/xca/

We use mkcert for this, it works wonderfully.

https://github.com/FiloSottile/mkcert

Debugging is pretty easy with something like Ray (https://myray.app/) or Laravel Herd (https://herd.laravel.com/, despite its name runs differnet php apps just fine).

When it coems to running different PHP versions, modern PHP development has largely moved to using Docker (ddev, for example: https://ddev.com/) for that, and there's plenty Docker images for old PHP versions so it's a non-issue. I'd also imagine it be difficult to get many other outdated programming languages via a package manager.

There's now the PHP Foundation, which while relatively new in its formation, has significantly boosted PHP development and I'd recommend donating if improving the language is important to you.

Do you already want to try the new version, which is currently in alpha state? With DDEV this is super simple, just paste one command into the terminal.

For development, I will still prefer to continue with DDEV (a tool that I highly recommend). But the adventure with SQLite was very interesting, it really helped me not to pollute my termux.

I use https://ddev.com for almost all of my web project development, which basically automates all of this. Per-project databases, web containers, plugins, etc, and it’s now using Traefik as its router.

I use it with ddev for local development.

https://ddev.readthedocs.io/

With the right combination of overlapping interests, a lot can get done and incredible things get build. See for example the Drupal book or DDEV--both are extremely active Drupal projects, with lots of community activity, outside of drupal.org.

You can go from 0 to 100 quickly with DDEV or Lando: - https://docs.lando.dev/ - https://ddev.readthedocs.io/

For local: have you tried DDEV? Or Lando? they seem pretty fast to me. https://github.com/drud/ddev

Lando works great with Linux, use DDEV for Mac. Both are Docker-based.

With DDEV you can create Docker PHP + NodeJS environments which run on every operating systems in the same way. These environment configuration can be shared via git which makes open source software DDEV a great and robust choice for team projects.