← Back to context

Comment by mitchellh

16 years ago

This project has been the love child of myself and John Bender (nickelcode.com) for the past 6 weeks. We're both daily HN readers and would like to use this as a starting point to show Vagrant to the public. Specifically, I'd like to open up to any questions and feedback, so that the HN community can get to know Vagrant. Your feedback is extremely valued. Thanks!

A bit of background on this project: I work at a development company (citrusbyte.com) in LA. I see new projects almost every couple months, and I'm often working on multiple projects simultaneously due to work, freelance, and personal projects. Managing the development environments between many projects on a local machine became a huge burden and a coworker once mentioned developing in a virtual machine. I thought this was a great idea, and Vagrant was eventually born from it.

Like I said before, feel free to ask any questions. If no questions, I value your feedback very highly, so please let me know what you think!

Thanks, Mitchell

10 comments

mitchellh

Reply
coconutrandom  16 years ago

This is so useful!!! I've been doing this manually for a select number of important projects. However, I'm not a Rails dev.

What would it take to work with [language/framework]?

I've skimmed over the docs and here [http://vagrantup.com/docs/getting-started/setup.html] it seems like instead of

  rails init

I could run

  django-admin startproject

  • mitchellh  16 years ago

    Of course! Vagrant is not specific to rails at all!

    The getting started screencast I made shows how to setup a LAMP environment: http://vimeo.com/9976342

    And the getting started guide shows a rails environment.

    Those should get you started on the path to python as well =]

    Mitchell

    • dlib  16 years ago

      Any plans for a repository of boxes? One with a LAMP stack, Rails stack, Django stack etc. I know I can roll my own and use chef there could be a community maintained repository of often used configurations.

      Also, in the screencast you use localhost to address the vm. Any way to assign another ip to the vm? In my current setup my vm's have altenative ips.

      1 reply →

  • johnbender  16 years ago

    This is one area where we really need feedback as most of the projects that Mitchell and I work on are Ruby/Rails (although Mitchells workload is much more diverse than my own).

    Stop by #vagrant if you have any questions!

dlib  16 years ago

Lately I've set up a virtual machine to set up a developing environment. In OSX I can get everything up and running with ports but it isolating it in a virtual machine running Debian or something feels safer and more robust.

I love this idea and will certainly check it out for my next project.

mtw  16 years ago

Hi Mitchell

I love this :-) have myself a bunch of slices and would make sense to consolidate them and run them with Vagrant (also would be less expensive too)

Have a question: does this run on a virtualized environment? For instance, if I get a big instance on EC2 or rackspacecloud, would virtual box work? Of course, this looks like it should be run on a dedicated "barebones" server, but I know I'll run into teams and webdevs who already have hosting at slicehost

  • mitchellh  16 years ago

    mtw,

    Thanks! Vagrant was really made to target the development environment, since the production world is pretty well covered in terms of deployment (whereas John and I thought that the development side of things had been neglected).

    But keyist answers your question best. I've quoted his response below:

      "Could you perhaps turn convert a Vagrant project into an EC2 instance for deployment?"

  That's where Chef comes in. Vagrant uses Chef (http://wiki.opscode.com/display/chef/Home) for provisioning VMs. It's basically software configuration management (same category as cfengine or Puppet) -- you write cookbooks that specify how a system should be set up (see http://github.com/opscode/cookbooks/raw/master/nginx/recipes... for an example).
  If you write your Chef configuration the right way (ie not hardcoding anything to a set of system specifications), you can take the same set of Chef cookbooks you write and deploy to EC2 or any other Linux box, virtual or no.
  So with Vagrant you can essentially pass around a virtual machine configuration amongst your team and be confident that the entire team is coding and testing in a near-exact replica of the production environment. Not that this was impossible before, but Vagrant streamlines the process.
  I've provisioned 20+ servers with Chef and once you have a solid base configuration you can take your attended time on a full server stack (nginx, memcached, post{gres,fix}, munin... the works, essentially) to less than 10 minutes.

crux_  16 years ago

Hiya Mitchell -- Sweet-looking project. What sort of effort would be required to use a Windows-based VM?

(Would you even recommend using Vagrant with Windows VMs, or is there any alternative I should look at? I'd like to automate my currently manual provisioning for various windows-based consulting work I do, but also set up VM-based continuous integration for some cross-platform software I'm writing.)

  • mitchellh  16 years ago

    The various "actions" which build up the behavior of the various Vagrant commands are tightly tied to a unix-based VM at the moment (see [1] for an example at the bottom).

    John and I have discussed this and we're trying to figure out a way to pull out this logic so its specific to each box, so windows VMs would be possible.

    That being said, assuming a windows VM has SSH, a quick hack would be to modify these actions to run the proper commands and it should work fine.

    [1]: http://github.com/mitchellh/vagrant/blob/master/lib/vagrant/...