LAMP on Virtual Machine, files and development environment in the host (Windows)

Events happening in the community are now at Drupal community events on www.drupal.org.
corbacho's picture

I know that Quickserver it's meant to have the dev environment also in the Virtual Machine, but I'm finding more suitable for my case to have the dev environment on Windows.

So I still use LAMP stack, Drush, Aegir, and all that *nix tools that come already with Quickserver but the files and development environment is Windows 7.

Other alternative I was considering is to have a separate dev machine on your LAN instead of a Virtual Machine and share files over the network.
But if you have a separate dev server file transfers/search are quite slow, so probably to have a Virtual Machine in a powerful host PC I'm finding it's the best solution (for personal use. Work teams is different)

To have this setup I was telling initially, basiclly you need 2 extra steps configuring your VM:

  1. To have access to the your Virtual Machine Network (from your Windows Machine) it's a no-brain setup: In the VM Settings, enable Bridge Networking. Start the VM machine, connect, guess the IP of your VM (or add it manually) and add it to /system32/etc/hosts in Windows.

    In my case this line:
    192.168.100.140 dev

    Then from Ubuntu you can access with http://localhost and from Windows with http://dev

  2. Then for share the folders in the VM settings-> Shared folders, select the folder and give exactly the name "shared" so it works out-of-the-box, and the shortcut in the Ubuntu desktop works.

To have dev files in my hard disk instead of VM hard disk, gives me some tranquility. What if VM get corrupted and I can't open the VM?
(Note that can be seen as an adventage http://crackingdrupal.com/blog/greggles/easier-and-safer-drupal-developm... )

All this is quite theorical still in my head, and let's see what kind of issues I have with file permissions, git, debugging, and other stuff that will come for sure.

I wonder what kind of experiences do you have with this setup? And what flaws do you see?

Comments

Good ideas...

MichaelCole's picture

Hi Corbacho,

All your ideas are valid, and would be appropriate for certain situations.

The vision behind Quickstart is something easy to start with: 1) Download 2) Press start 3) Start coding. From this vision, I didn't want to require users to read instructions, install software, or configure things on their local box.

Re: corrupted disk - I'd recommend always saving code to a version control system (cvs, svn, ect.). This is how I alleviate that problem on all my dev computers.

Re: bridged networking - That's a great idea, I'll add some instructions in the next release of Quickstart to explain how to do this.

So I think your approach would be valid for certain situations, but probably not the same situations as Quickstart.

Cheers,

Mike

Quickstart Drupal Development Environment

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: