Permalink
Browse files

added vagrantfile for testing

  • Loading branch information...
1 parent fd810ef commit 18e708a3c5f6964ee33ad705c8cf0cef5bb77848 @auser committed Sep 4, 2011
Showing with 109 additions and 0 deletions.
  1. +2 −0 .gitignore
  2. +1 −0 Gemfile
  3. +20 −0 Gemfile.lock
  4. +86 −0 Vagrantfile
View
@@ -1,4 +1,6 @@
examples-private/
+.vagrant
+vendor/cache
/trash/
rdoc/*
.com.apple.timemachine.supported
View
@@ -15,6 +15,7 @@ group :test do
gem 'mocha'
gem 'right_http_connection'
gem "jnunemaker-matchy", "~> 0.4.0"
+ gem 'vagrant'
end
group :development do
View
@@ -12,19 +12,38 @@ GEM
addressable (2.2.6)
amazon-ec2 (0.9.17)
xml-simple (>= 1.0.12)
+ archive-tar-minitar (0.5.2)
crack (0.1.8)
+ erubis (2.7.0)
fakeweb (1.3.0)
+ ffi (1.0.9)
git-style-binaries (0.1.11)
shoulda
trollop
+ i18n (0.5.0)
jnunemaker-matchy (0.4.0)
json (1.5.3)
mocha (0.9.12)
+ net-scp (1.0.4)
+ net-ssh (>= 1.99.1)
+ net-ssh (2.1.4)
rcov (0.9.9)
rdoc (3.9.4)
right_http_connection (1.3.0)
shoulda (2.11.3)
+ thor (0.14.6)
trollop (1.16.2)
+ vagrant (0.8.6)
+ archive-tar-minitar (= 0.5.2)
+ erubis (~> 2.7.0)
+ i18n (~> 0.5.0)
+ json (~> 1.5.1)
+ net-scp (~> 1.0.4)
+ net-ssh (~> 2.1.4)
+ thor (~> 0.14.6)
+ virtualbox (~> 0.9.1)
+ virtualbox (0.9.2)
+ ffi (~> 1.0.9)
webmock (1.6.4)
addressable (~> 2.2, > 2.2.5)
crack (>= 0.1.7)
@@ -45,5 +64,6 @@ DEPENDENCIES
rdoc
right_http_connection
shoulda
+ vagrant
webmock
xml-simple
View
@@ -0,0 +1,86 @@
+Vagrant::Config.run do |config|
+ # All Vagrant configuration is done here. The most common configuration
+ # options are documented and commented below. For a complete reference,
+ # please see the online documentation at vagrantup.com.
+
+ # Every Vagrant virtual environment requires a box to build off of.
+ config.vm.box = "base"
+
+ # The url from where the 'config.vm.box' box will be fetched if it
+ # doesn't already exist on the user's system.
+ # config.vm.box_url = "http://domain.com/path/to/above.box"
+
+ # Boot with a GUI so you can see the screen. (Default is headless)
+ # config.vm.boot_mode = :gui
+
+ # Assign this VM to a host only network IP, allowing you to access it
+ # via the IP.
+ config.vm.network "33.33.33.10"
+
+ # Forward a port from the guest to the host, which allows for outside
+ # computers to access the VM, whereas host only networking does not.
+ # config.vm.forward_port "http", 80, 8080
+
+ # Share an additional folder to the guest VM. The first argument is
+ # an identifier, the second is the path on the guest to mount the
+ # folder, and the third is the path on the host to the actual folder.
+ config.vm.share_folder "v-data", "/vagrant_data", ".", :nfs => true
+
+ # Enable provisioning with Puppet stand alone. Puppet manifests
+ # are contained in a directory path relative to this Vagrantfile.
+ # You will need to create the manifests directory and a manifest in
+ # the file base.pp in the manifests_path directory.
+ #
+ # An example Puppet manifest to provision the message of the day:
+ #
+ # # group { "puppet":
+ # # ensure => "present",
+ # # }
+ # #
+ # # File { owner => 0, group => 0, mode => 0644 }
+ # #
+ # # file { '/etc/motd':
+ # # content => "Welcome to your Vagrant-built virtual machine!
+ # # Managed by Puppet.\n"
+ # # }
+ #
+ # config.vm.provision :puppet do |puppet|
+ # puppet.manifests_path = "manifests"
+ # puppet.manifest_file = "base.pp"
+ # end
+
+ # Enable provisioning with chef solo, specifying a cookbooks path (relative
+ # to this Vagrantfile), and adding some recipes and/or roles.
+ #
+ # config.vm.provision :chef_solo do |chef|
+ # chef.cookbooks_path = "cookbooks"
+ # chef.add_recipe "mysql"
+ # chef.add_role "web"
+ #
+ # # You may also specify custom JSON attributes:
+ # chef.json = { :mysql_password => "foo" }
+ # end
+
+ # Enable provisioning with chef server, specifying the chef server URL,
+ # and the path to the validation key (relative to this Vagrantfile).
+ #
+ # The Opscode Platform uses HTTPS. Substitute your organization for
+ # ORGNAME in the URL and validation key.
+ #
+ # If you have your own Chef Server, use the appropriate URL, which may be
+ # HTTP instead of HTTPS depending on your configuration. Also change the
+ # validation key to validation.pem.
+ #
+ # config.vm.provision :chef_client do |chef|
+ # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
+ # chef.validation_key_path = "ORGNAME-validator.pem"
+ # end
+ #
+ # If you're using the Opscode platform, your validator client is
+ # ORGNAME-validator, replacing ORGNAME with your organization name.
+ #
+ # IF you have your own Chef Server, the default validation client name is
+ # chef-validator, unless you changed the configuration.
+ #
+ # chef.validation_client_name = "ORGNAME-validator"
+end

0 comments on commit 18e708a

Please sign in to comment.