diff --git a/_includes/header.html b/_includes/header.html index 16e957024..61023615d 100644 --- a/_includes/header.html +++ b/_includes/header.html @@ -27,6 +27,8 @@
  • get started
  • user guide
  • contribute
  • +
  • faq
  • +
  • support
  • code
  • diff --git a/contribute.md b/contribute.md index 82e80c041..e81bbfa9c 100644 --- a/contribute.md +++ b/contribute.md @@ -4,10 +4,5 @@ title: Contribute --- Vagrant needs you! -We're trying to build something great to change the way developers work. -But we're just two guys, and we know there is a lot of growing up we have -to do! If you've got an idea, a bug report, or just want to dig in and hack -on Vagrant, you are welcome to! - Visit [Vagrant on GitHub](http://github.com/mitchellh/vagrant) to report any issues or to grab the code to begin hacking. \ No newline at end of file diff --git a/faq.md b/faq.md new file mode 100644 index 000000000..443eb059a --- /dev/null +++ b/faq.md @@ -0,0 +1,41 @@ +--- +layout: default +title: FAQ +--- + +

    FAQ

    + +### Why should I use Vagrant? What I'm doing now works just fine. + +One could say that web development was working just fine prior to +the rise of MVC and opinionated development frameworks and they would +be speaking the truth as well. Vagrant is not trying to change the way +you work because its wrong, per se, but move web development forward +by providing isolated environments which are easy to build, portable, +and lightweight. + +### Vagrant would be so much better if it had feature `X`! + +Vagrant is open source and released under a permissive [license](/license.html), +so feel free to modify it and add the feature! Open up a ticket +explaining why the feature adds value to Vagrant with a link to the +patch you'd like us to merge in and we probably will. If you aren't comfortable +adding the feature yourself, still make a ticket and if its compelling +enough, someone will add it in for you. + +### Don't virtual machines slow down your main development machine? + +The short answer: no. Longer answer: Given a big enough and busy enough virtual machine... perhaps. But through real-world +usage, we've found that most virtual machines are small, using 256 to 500 MB or RAM, +and typically are running mostly idle processes. Its not as if the virtual machines +are running 3D games (although I suppose you could try it)! + +### Virtual machines take up way too much hard drive space! + +An average virtual machine that Vagrant provisions is about 500 MB of physical +disk space total (although the virtual drive had a capacity +of 40 GB). Sure, if you have 10 vagrant projects with their virtual environments built, +this is 5 GB, but its still only 5 GB. And don't forget that Vagrant allows you to complete +tear down the environment and rebuild it in a flash, so you shouldn't ever even need all +those environments built at the same time. Just run `vagrant up` when you need a virtual +machine and disk space will be kept low. \ No newline at end of file diff --git a/support.md b/support.md new file mode 100644 index 000000000..677128ab1 --- /dev/null +++ b/support.md @@ -0,0 +1,13 @@ +--- +layout: default +title: Support +--- + +

    Support

    + +Vagrant is a new and potentially complex tool. Need help learning how to +use it? There is a helpful community waiting to answer your questions. + +* `#vagrant` on Freenode for real-time chat +* `Google Group` for a mailing list +* `Lighthouse` for reporting bugs \ No newline at end of file