I've been able to follow the instructions so far on configuring Homestead on a per project basis, and now have multiple Laravel projects with their own Homestead environments running smoothly on my local machines.
Now I'm wanting to distribute the source code of one of these projects and I'm a little confused on how to do it.
Am I shipping the Vagrantfile and a Homestead.yaml.example with the project (because it's already specified in composer, but assuming they don't have composer until Homestead is installed)?
I don't think the developer cloning the project should have to run the php commands to make the Vagrantfile and Homestead.yaml.example file, because again, I've got to assume they don't have PHP until Homestead is up and running.
I want to include the environment to the developers because we work on different operating systems and I'm trying to make it as easy as possible for the Windows developers who don't have PHP installed, or composer, and would have to rely on the Homestead service for those.
It's not difficult to create your own custom box. This would probably be the most straightforward way to provide the required environment, if none of the existing Homestead boxes are sufficiently provisioned for your project. I don't think there is a way to spare the developer from learning a little bit about Homestead and Vagrant. This tutorial presents the process in a fairly clear fashion:
https://scotch.io/tutorials/how-to-create-a-vagrant-base-box-from-an-existing-one
Please or to participate in this conversation.