Created
December 21, 2012 13:57
-
-
Save Natim/4352993 to your computer and use it in GitHub Desktop.
Vagrantfile
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# -*- mode: ruby -*- | |
# Generated with /home/rhubscher/novapost/postbox/bin/postbox-configure --output-dir=var/vm/postbox --preset=vagrantfile-postbox vagrantfile | |
# **YOU SHOULD NOT EDIT THIS FILE MANUALLY.** | |
# You had better edit templates and presets, then run the generator again. | |
# 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 = "postbox" | |
# 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 = "/home/rhubscher/novapost/postbox/var/vm/vagrant-debian-6.0.5-amd64.box" | |
# Boot with a GUI so you can see the screen. (Default is headless) | |
config.vm.boot_mode = :gui | |
config.ssh.forward_agent = true | |
# 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, "34.34.34.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, 8080 | |
# VM hardware configuration. | |
config.vm.customize ["modifyvm", :id, "--memory", 512] | |
config.vm.customize ["modifyvm", :id, "--cpus", 1] | |
config.vm.customize ["modifyvm", :id, "--vram", 16] | |
# 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" | |
# Provisioning is done on the VM via SSH, not triggered with Vagrant on | |
# startup, i.e. just like it would be done in PROD environment. | |
# Moreover, sometimes you work on provisioning on the VM, performing some | |
# tasks onto the VM. If you haven't committed/pushed your changes yet and | |
# the VM restarts for any reason, there is a risk you lose your work. | |
end |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment