What to include and what not to include in the repository when working with PHPStorm+Git+Laravel+Composer+Vagrant?

Question

git

I started working with such a set of things and in the end I wonder, what should be included in the repository when creating a project from scratch with this configuration? I work in the win environment, so I even think about including there, if not php in its entirety, then php.ini for sure, since different projects require different environments and different versions of the language - not in the sense that working with projects in the described configuration, but in the sense that it makes no sense to install one global copy of php on the entire working computer, since a project that requires its own environment can live in the next folder.
In general, on the one hand, you don’t want to inflate the repositories, but on the other hand, how is this most correctly organized? An important clarification is that several people will work with the repository, so the greatest transparency is needed so that everyone always and everywhere understands which path the project has taken since the environment was set up for it.

Answer 1

I work in the win environment , so I’m even thinking about including there, if not php in its entirety, then php.ini for sure, since different projects require different environments and different versions of the language - not in the sense that working with projects in the described configuration, but in the sense that it makes no sense to install one global copy of php on the entire working computer, since a project that requires its own environment can live in the next folder.

When using vagrant, do you precisely configure the virtual machine for the project?
The vagrant instructions should contain the configuration of all software for your project (mysql, php, nginx) and the initial steps to run in the project (executing the composer install, npm install, gulp commands).
Purpose: to have a working project immediately when starting the virtual machine.