Using for something other than Puppet or Chef

[kgleason]

I took a course @ Ohio Linux 2012 that sort of introduced me to this project. I'm in the process of setting up my dev-ops environment, and I certainly intend to use this for puppet dev & testing.

However, if I understand this project properly, I find myself wondering if some of my developer friends & co-workers might not like something like this.

What I'm envisioning is a web developer who builds LAMP applications. WOuld it be feasible to use Vagrant-hitch to hitch up the local source files for the app to a LAMP VM?

[azizshamim]

Absolutely, there's a mounts: data point that is helpful in situations like these. Mount the local source file to a mounted directory on the virtualbox and configure the virtualbox to use that mounted directory as the DocumentRoot in apache.
Something like this (mount takes paths relative to the Vagrantfile):

lamp-dev:
  orgname: org.test
  ports:
    http:
      host: 10080
      guest: 80
    https:
      host: 10443
      guest: 443
  mounts:
    app1:
      host: ../www/
      guest: /var/www/app1
      owner: apache

Would a more detailed blog article be helpful?

[kgleason]

Perhaps a blog article might be helpful for me eventually. I'm still trying to figure out how to get it work with puppet, but to be fair, I am learning vagrant, veewee, vagrant-hitch, and puppet all in one fell swoop, and I think I've bitten off more than I can chew.

I do appreciate the offer though.