| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990 |
- # -*- mode: ruby -*-
- # vi: set ft=ruby :
- 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 = "lucid32"
- # 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://files.vagrantup.com/lucid32.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. Host-only networks can talk to the host machine as well as
- # any other machines on the same network, but cannot be accessed (through this
- # network interface) by any external networks.
- # config.vm.network :hostonly, "192.168.33.10"
- # Assign this VM to a bridged network, allowing you to connect directly to a
- # network using the host's network device. This makes the VM appear as another
- # physical device on your network.
- # config.vm.network :bridged
- # 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 80, 8081
- # Hostname
- config.vm.host_name = "zf1.dev"
- # Pass custom arguments to VBoxManage before booting VM
- config.vm.customize [
- # 'modifyvm', :id, '--chipset', 'ich9', # solves kernel panic issue on some host machines
- # '--uartmode1', 'file', 'C:\\base6-console.log' # uncomment to change log location on Windows
- "setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root", "1"
- ]
- # 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", "../data"
- # 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 lucid32.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 = "lucid32.pp"
- # end
- config.vm.provision :puppet do |puppet|
- puppet.manifests_path = "puppet/manifests"
- puppet.manifest_file = "default.pp"
- end
- # config.vm.provision :puppet do |puppet|
- # puppet.manifests_path = "puppet/manifests"
- # puppet.module_path = "puppet/modules"
- # puppet.manifest_file = "zf1.pp"
- # puppet.options = [
- # '--verbose',
- # #'--debug',
- # # '--graph',
- # # '--graphdir=/vagrant/puppet/graphs'
- # ]
- # end
- end
|