Hi, Wil Moore III wrote: > weierophinney wrote: > > That said, I also have some colleagues and friends who work on teams > > that use VM environments, and swear by it. > > My team goes the VM route as well. We each have a VM w/ an Ubuntu bare > minimum install. There is a baseline image that we all use; however, we've > documented the install process well enough that one does not necessarily > need the image. We install from the Ubuntu minimal cd and "sudo apt-get
Are you using IDEs or just editors? We also tried to use VMs, but we run into a problem we couldn't solve: The application server is running in the VM. So it needs to have access to your source code. So how do you share your working copy with the application server? For example: The developer is on Windows. He might use some IDEs like Zend Studio, PhpEd or just an editor like UltraEdit, Notepad. How does he access the source code? Will he have a local working copy? If yes, how does he synchronize the working copy in the VM with the local working copy? In our test, this became a real problem: 1.) Developer makes local changes. 2.) He commits into his local GIT repository. 3.) He switched to his VM and updates the working copy of the application server in the VM. This requires access from the VM to the GIT repository. So he might have to copy files between the host and the VM, if he cannot access it via network. 4.) The developer runs the application to see if everything is fine. 5.) If everything is fine, he will commit the changes into our company repository. If he recognize in step 4 that he has forgotten a ";"... he need to switch back to his editor/IDE, change the code re-do step 2-4... We tried to use shares: - Working copy is in the VM. The VM shares the working copy to the host system, so the local editor/IDE can access the source code. - Working copy is on the host. The host is sharing the working copy to the VM, so the application server is able to access the source code. Nothing worked for us. We had many problems (LOCKING problems for example). -- Regards, Thomas
