tnargav 1.2.3 → 1.3.3

data/website/docs/source/v2/vmware/configuration.html.md

@@ -0,0 +1,91 @@
+---
+page_title: "Configuration- VMware Provider"
+sidebar_current: "vmware-configuration"
+---
+
+# Configuration
+
+While VMware providers are a drop-in replacement for VirtualBox, there are
+some additional features that are exposed that allow you to more finely
+configure VMware-specific aspects of your machines.
+
+## "VMware Fusion.app" Location
+
+The provider by default looks for VMware Fusion in "/Applications" and
+"~/Applications." If you put your applications in some other place, you'll
+have to manually tell Vagrant where VMware Fusion is.
+
+This can be done with the `VAGRANT_VMWARE_FUSION_APP` environmental variable.
+
+For example, if you put your applications in an "/Apps" directory, you
+would configure Vagrant like this:
+
+```
+$ export VAGRANT_VMWARE_FUSION_APP="/Apps/VMware Fusion.app"
+$ vagrant up --provider=vmware_fusion
+```
+
+## VM Clone Directory
+
+By default, the VMware provider will clone the VMware VM in the box
+to the ".vagrant" folder relative to the folder where the Vagrantfile is.
+Usually, this is fine. For some people, for example those who use a
+differential backup software such as Time Machine, this is very annoying
+because you can't regularly ignore giant virtual machines as part of backups.
+
+The directory where the provider clones the virtual machine can be
+customized by setting the `VAGRANT_VMWARE_CLONE_DIRECTORY` environmental
+variable. This doesn't need to be unique per project. Each project will
+get a different sub-directory within this folder. Therefore, it is safe to
+set this systemwide.
+
+## Virtual Machine GUI
+
+The VMware provider generally starts the virtual machines
+in headless mode. If you'd like to see the UI because you're running
+a desktop within the VM, or if you need to debug potential boot issues
+with the VM, you can configure the VMware provider to boot with the
+GUI:
+
+```ruby
+config.vm.provider "vmware_fusion" do |v|
+  v.gui = true
+end
+```
+
+Use "vmware_workstation" if you're using VMware workstation.
+
+## VMX Customization
+
+If you want to add or remove specific keys from the VMX file, you can do
+that:
+
+```ruby
+config.vm.provider "vmware_fusion" do |v|
+  v.vmx["custom-key"]  = "value"
+  v.vmx["another-key"] = nil
+end
+```
+
+Use "vmware_workstation" if you're using VMware workstation.
+
+In the example above, the "custom-key" key will be set to "value" and the
+"another-key" key will be removed from the VMX file.
+
+VMX customization is done as the final step before the VMware machine is
+booted, so you have the ability to possibly undo or misconfigure things
+that Vagrant has set up itself.
+
+VMX is an undocumented format and there is no official reference for
+the available keys and values. This customization option is exposed for
+people who have knowledge of exactly what they want.
+
+The most common keys people look for are setting memory and CPUs.
+The example below sets both:
+
+```ruby
+config.vm.provider "vmware_fusion" do |v|
+  v.vmx["memsize"] = "1024"
+  v.vmx["numvcpus"] = "2"
+end
+```

data/website/docs/source/v2/vmware/index.html.md

@@ -0,0 +1,30 @@
+---
+page_title: "VMware Provider"
+sidebar_current: "vmware"
+---
+
+# VMware
+
+[HashiCorp](http://www.hashicorp.com) develops an official
+[VMware Fusion](http://www.vmware.com/products/fusion/overview.html)
+and [VMware Workstation](http://www.vmware.com/products/workstation/) 
+[provider](/v2/providers/index.html) for Vagrant. This provider allows
+Vagrant to power VMware based machines and take advantage of the
+improved stability and performance that VMware software offers.
+
+Learn more about the VMware providers on the
+[VMware provider](http://www.vagrantup.com/vmware) page on
+the Vagrant website.
+
+This provider is a drop-in replacement for VirtualBox, meaning that every
+VirtualBox feature that Vagrant supports is fully functional in VMware as
+well. However, there are some VMware-specific things such as box formats,
+configurations, etc. that are documented here.
+
+The VMware provider is currently compatible only with Fusion 5 or Workstation 9.
+Fusion and Workstation must be purchased and installed separately prior to using the
+provider. If the proper VMware software isn't properly installed, or an invalid version is
+installed, the provider will give you a human-friendly error message.
+
+Use the navigation to the left to find a specific VMware topic to read
+more about.

data/website/docs/source/v2/vmware/installation.html.md

@@ -0,0 +1,40 @@
+---
+page_title: "Installation - VMware Provider"
+sidebar_current: "vmware-installation"
+---
+
+# Installation
+
+The VMware provider is installed using
+[standard plugin installation procedures](/v2/plugins/usage.html).
+In addition to installing the plugin, a license must be provided so that
+it can be loaded properly.
+
+To purchase a license, visit the [Vagrant VMware provider](http://www.vagrantup.com/vmware)
+page. After purchasing a license, a link to download it will be emailed
+to you. Download this file.
+
+Installing the plugin and license is easy using the `vagrant plugin`
+interface. Both steps are shown below. Note that the plugin name is different
+depending on the provider you're using. If you're using the Fusion provider,
+it is `vagrant-vmware-fusion`. If you're using the Workstation provider,
+it is `vagrant-vmware-workstation`.
+
+```
+$ vagrant plugin install vagrant-vmware-fusion
+...
+$ vagrant plugin license vagrant-vmware-fusion license.lic
+...
+```
+
+For licensing, the first parameter is the name of the plugin, which is
+`vagrant-vmware-fusion` for the VMware Fusion provider, or `vagrant-vmware-workstation`
+for the VMware Workstation provider. The second parameter is the path to the license itself.
+
+You can verify the license is properly installed by running any
+Vagrant command, such as `vagrant plugin list`. The VMware
+provider will show an error message if you are missing a license or using an
+invalid license.
+
+If there are problems installing the plugin, please contact
+[support](http://www.vagrantup.com/support.html).

data/website/docs/source/v2/vmware/known-issues.html.md

@@ -0,0 +1,21 @@
+---
+page_title: "Known Issues - VMware Provider"
+sidebar_current: "vmware-known-issues"
+---
+
+# Known Issues
+
+This page tracks some known issues or limitations of the VMware providers.
+Note that none of these are generally blockers to using the provider, but
+are good to know.
+
+## Forwarded Ports Failing in Workstation on Windows
+
+VMware Workstation has a bug on Windows where forwarded ports don't work
+properly. Vagrant actually works around this bug and makes them work. However,
+if you run the virtual network editor on Windows, the forwarded ports will
+suddenly stop working.
+
+In this case, run `vagrant reload` and things will begin working again.
+
+This issue has been reported to VMware, but a fix hasn't been released yet.

data/website/docs/source/v2/vmware/usage.html.md

@@ -0,0 +1,27 @@
+---
+page_title: "Usage - VMware Provider"
+sidebar_current: "vmware-usage"
+---
+
+# Usage
+
+The VMware providers are used just like any other provider. Please
+read the general [basic usage](/v2/providers/basic_usage.html) page for
+providers.
+
+The value to use for the `--provider` flag is `vmware_fusion` for VMware
+Fusion, and `vmware_workstation` for VMware Workstation.
+
+<p>
+To get started, a 64-bit Ubuntu 12.04 LTS VMware box is available at:
+<a href="http://files.vagrantup.com/precise64_vmware.box">http://files.vagrantup.com/precise64_vmware.box</a>
+</p>
+
+<div class="alert alert-info">
+	<p>
+		<strong>Note:</strong> At some point in the future, the providers
+		will probably be merged into a single `vagrant-vmware` plugin. For now,
+		the Workstation and Fusion codebases are different enough that they
+		are separate plugins.
+	</p>
+</div>

data/website/docs/source/v2/why-vagrant/index.html.md

@@ -0,0 +1,46 @@
+---
+page_title: "Why Vagrant?"
+sidebar_current: "why"
+---
+
+# Why Vagrant?
+
+Vagrant provides easy to configure, reproducible, and portable work environments
+built on top of industry-standard technology and
+controlled by a single consistent workflow to help maximize the productivity
+and flexibility of you and your team.
+
+To achieve its magic, Vagrant stands on the shoulders of giants. Machines
+are provisioned on top of VirtualBox, VMware, AWS, or
+[any other provider](/v2/providers/index.html). Then, industry-standard
+[provisioning tools](/v2/provisioning/index.html)
+such as shell scripts, Chef, or Puppet, can be used to automatically install
+and configure software on the machine.
+
+## How Vagrant Benefits You
+
+If you're a **developer**, Vagrant will isolate dependencies and their
+configuration within a single disposable, consistent environment, without
+sacrificing any of the tools you're used to working with (editors, browsers,
+debuggers, etc.). Once you or someone else creates a single [Vagrantfile](/v2/vagrantfile/index.html), you just need to `vagrant up` and everything is installed and
+configured for you to work. Other members of your team create their
+development environments from the same configuration, so whether you're working
+on Linux, Mac OS X, or Windows, all your team members are running code in
+the same environment, against the same dependencies, all configured the same way.
+Say goodbye to "works on my machine" bugs.
+
+If you're an **operations engineer**, Vagrant gives you a disposable environment
+and consistent workflow for developing and testing infrastructure management
+scripts. You can quickly test things like shell scripts, Chef cookbooks,
+Puppet modules, and more using local virtualization such as VirtualBox or
+VMware. Then, with the _same configuration_, you can test these scripts
+on remote clouds such as AWS or RackSpace with the _same workflow_. Ditch
+your custom scripts to recycle EC2 instances, stop juggling SSH prompts
+to various machines, and start using Vagrant to bring sanity to your life.
+
+If you're a **designer**, Vagrant will automatically setup everything required
+for that web app in order for you to focus on doing what you do best:
+design. Once a developer configures Vagrant, you don't need to worry about
+how to get that app running ever again. No more bothering other developers
+to help you fix your environment so you can test designs. Just check out the
+code, `vagrant up`, and start designing.

data/website/www/.buildpacks

@@ -0,0 +1,2 @@
+https://github.com/heroku/heroku-buildpack-ruby.git
+https://github.com/hashicorp/heroku-buildpack-middleman.git

data/website/www/Gemfile

@@ -0,0 +1,15 @@
+source 'https://rubygems.org'
+
+gem "less", "~> 2.2.2"
+gem "middleman", "~> 3.1.5"
+gem "middleman-blog", "~> 3.3.0"
+gem "middleman-minify-html", "~> 3.1.1"
+gem "nokogiri", "~> 1.6.0"
+gem "rack-contrib", "~> 1.1.0"
+gem "redcarpet", "~> 3.0.0"
+gem "therubyracer", "~> 0.12.0"
+gem "thin", "~> 1.5.0"
+
+group :development do
+  gem "highline", "~> 1.6.15"
+end

data/website/www/Gemfile.lock

@@ -0,0 +1,123 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (3.2.14)
+      i18n (~> 0.6, >= 0.6.4)
+      multi_json (~> 1.0)
+    chunky_png (1.2.8)
+    coffee-script (2.2.0)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.6.3)
+    commonjs (0.2.7)
+    compass (0.12.2)
+      chunky_png (~> 1.2)
+      fssm (>= 0.2.7)
+      sass (~> 3.1)
+    daemons (1.1.9)
+    eventmachine (1.0.3)
+    execjs (1.4.0)
+      multi_json (~> 1.0)
+    ffi (1.9.0)
+    fssm (0.2.10)
+    haml (4.0.3)
+      tilt
+    highline (1.6.19)
+    hike (1.2.3)
+    i18n (0.6.5)
+    kramdown (1.1.0)
+    less (2.2.2)
+      commonjs (~> 0.2.6)
+    libv8 (3.16.14.3)
+    listen (1.2.3)
+      rb-fsevent (>= 0.9.3)
+      rb-inotify (>= 0.9)
+      rb-kqueue (>= 0.2)
+    middleman (3.1.5)
+      coffee-script (~> 2.2.0)
+      compass (>= 0.12.2)
+      execjs (~> 1.4.0)
+      haml (>= 3.1.6)
+      kramdown (~> 1.1.0)
+      middleman-core (= 3.1.5)
+      middleman-more (= 3.1.5)
+      middleman-sprockets (>= 3.1.2)
+      sass (>= 3.1.20)
+      uglifier (~> 2.1.0)
+    middleman-blog (3.3.0)
+      middleman-core (~> 3.0)
+      middleman-more (~> 3.0)
+      tzinfo (~> 0.3.0)
+    middleman-core (3.1.5)
+      activesupport (~> 3.2.6)
+      bundler (~> 1.1)
+      i18n (~> 0.6.1)
+      listen (~> 1.2.2)
+      rack (>= 1.4.5)
+      rack-test (~> 0.6.1)
+      thor (>= 0.15.2, < 2.0)
+      tilt (~> 1.3.6)
+    middleman-minify-html (3.1.1)
+      middleman-core (~> 3.0)
+    middleman-more (3.1.5)
+    middleman-sprockets (3.1.4)
+      middleman-core (>= 3.0.14)
+      middleman-more (>= 3.0.14)
+      sprockets (~> 2.1)
+      sprockets-helpers (~> 1.0.0)
+      sprockets-sass (~> 1.0.0)
+    mini_portile (0.5.1)
+    multi_json (1.8.0)
+    nokogiri (1.6.0)
+      mini_portile (~> 0.5.0)
+    rack (1.5.2)
+    rack-contrib (1.1.0)
+      rack (>= 0.9.1)
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rb-fsevent (0.9.3)
+    rb-inotify (0.9.2)
+      ffi (>= 0.5.0)
+    rb-kqueue (0.2.0)
+      ffi (>= 0.5.0)
+    redcarpet (3.0.0)
+    ref (1.0.5)
+    sass (3.2.10)
+    sprockets (2.10.0)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sprockets-helpers (1.0.1)
+      sprockets (~> 2.0)
+    sprockets-sass (1.0.1)
+      sprockets (~> 2.0)
+      tilt (~> 1.1)
+    therubyracer (0.12.0)
+      libv8 (~> 3.16.14.0)
+      ref
+    thin (1.5.1)
+      daemons (>= 1.0.9)
+      eventmachine (>= 0.12.6)
+      rack (>= 1.0.0)
+    thor (0.18.1)
+    tilt (1.3.7)
+    tzinfo (0.3.37)
+    uglifier (2.1.2)
+      execjs (>= 0.3.0)
+      multi_json (~> 1.0, >= 1.0.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  highline (~> 1.6.15)
+  less (~> 2.2.2)
+  middleman (~> 3.1.5)
+  middleman-blog (~> 3.3.0)
+  middleman-minify-html (~> 3.1.1)
+  nokogiri (~> 1.6.0)
+  rack-contrib (~> 1.1.0)
+  redcarpet (~> 3.0.0)
+  therubyracer (~> 0.12.0)
+  thin (~> 1.5.0)

data/website/www/Procfile

@@ -0,0 +1 @@
+web: bundle exec thin start -p $PORT

data/website/www/README.md

@@ -0,0 +1,26 @@
+# VagrantUp.com
+
+This is the repository for the [Vagrant website](http://www.vagrantup.com).
+
+This is a [Middleman](http://middlemanapp.com) project, which builds a static
+site from these source files. The site is hosted on [Heroku](http://heroku.com)
+and then fronted by [Fastly](http://fastly.com).
+
+## Contributions Welcome!
+
+If you find a typo or you feel like you can improve the HTML, CSS, or
+JavaScript, we welcome contributions. Feel free to open issues or pull
+requests like any normal GitHub project, and we'll merge it in.
+
+## Running the Site Locally
+
+Running the site locally is simple. Clone this repo and run the following
+commands:
+
+```
+$ bundle
+$ bundle exec middleman server
+```
+
+Then open up `localhost:4567`. Note that some URLs you may need to append
+".html" to make them work (in the navigation and such).

data/website/www/config.rb

@@ -0,0 +1,88 @@
+###
+# Compass
+###
+
+# Susy grids in Compass
+# First: gem install susy --pre
+# require 'susy'
+
+# Change Compass configuration
+# compass_config do |config|
+#   config.output_style = :compact
+# end
+
+###
+# Page options, layouts, aliases and proxies
+###
+
+# Per-page layout changes:
+#
+# With no layout
+# page "/path/to/file.html", :layout => false
+#
+# With alternative layout
+# page "/path/to/file.html", :layout => :otherlayout
+#
+# A path which all have the same layout
+# with_layout :admin do
+#   page "/admin/*"
+# end
+
+# Proxy (fake) files
+# page "/this-page-has-no-template.html", :proxy => "/template-file.html" do
+#   @which_fake_page = "Rendering a fake page with a variable"
+# end
+
+###
+# Helpers
+###
+
+# Automatic image dimensions on image_tag helper
+# activate :automatic_image_sizes
+
+# Methods defined in the helpers block are available in templates
+# helpers do
+#   def some_helper
+#     "Helping"
+#   end
+# end
+
+set :css_dir, 'stylesheets'
+set :js_dir, 'javascripts'
+set :images_dir, 'images'
+
+# Use the RedCarpet Markdown engine
+set :markdown_engine, :redcarpet
+set :markdown, :fenced_code_blocks => true
+
+# Enable the blog and set the time zone so that post times appear
+# correctly.
+Time.zone = "America/Los_Angeles"
+
+activate :blog do |b|
+  b.layout = "blog_post"
+  b.permalink = ":title.html"
+  b.prefix = "blog"
+end
+
+# Build-specific configuration
+configure :build do
+  activate :asset_hash
+  activate :minify_css
+  activate :minify_html
+  activate :minify_javascript
+
+  # Enable cache buster
+  # activate :cache_buster
+
+  # Use relative URLs
+  # activate :relative_assets
+
+  # Compress PNGs after build
+  # First: gem install middleman-smusher
+  # require "middleman-smusher"
+  # activate :smusher
+
+  # Or use a different image path
+  # set :http_path, "/Content/images/"
+end