This wouldn't be useful for starting up a new PHP project. Instead, it'd be great for situations where you've got a dozen different projects that you work on every few months to a year, all with different dependencies and settings, services (dbs, kv stores, whatever), env vars, and so on.
I've definitely spent a few hours, when going back to a project after a few months, just trying to remember exactly what the environmental assumptions and requirements are. Being able to just pop straight back into development without any of that is amazing.
Having to do the infra-as-code of a system that didn't have it and is already live is a royal pain. If you foresee you will end up having any level of complexity, you actually save time doing it from the beginning. It's just a way of avoiding tech debt down the line.
Which could vary from "very easy" to "does anyone know who put this file there, and why, 9 months ago?".