-
Notifications
You must be signed in to change notification settings - Fork 7
/
Vagrantfile
122 lines (101 loc) · 4.47 KB
/
Vagrantfile
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
# -*- mode: ruby -*-
# vi: set ft=ruby :
# See TESTING.md file.
Vagrant.configure('2') 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.
config.vm.hostname = 'opendkim.local'
# Opscode Chef Vagrant box to use.
# More boxes here: https://github.com/opscode/bento
opscode_box = 'opscode-ubuntu-12.04'
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = opscode_box
# 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://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/'\
"#{opscode_box.sub('-', '_')}_chef-provisionerless.box"
# 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 :private_network, ip: '10.73.57.123'
# Create a public network, which generally matched to bridged network. Bridged
# networks make the machine appear as another physical device on your network.
# config.vm.network :public_network
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing 'localhost:8080' will access port 80 on the guest machine.
# config.vm.network :forwarded_port, guest: 80, host: 8080, auto_correct: true
# The time in seconds that Vagrant will wait for the machine to boot and be
# accessible.
config.vm.boot_timeout = 120
# Share an additional folder to the guest VM. The first argument is the path
# on the host to the actual folder. The second argument is the path on the
# guest to mount the folder. And the optional third argument is a set of
# non-required options.
# config.vm.synced_folder '../data', '/vagrant_data'
# Provider-specific configuration so you can fine-tune various backing
# providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
# config.vm.provider :virtualbox do |vb|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.memory = 1024
# end
#
# View the documentation for the provider you're using for more information on
# available options.
# Install the latest version of Chef.
config.omnibus.chef_version = :latest
# Enabling the Berkshelf plugin. To enable this globally, add this
# configuration option to your ~/.vagrant.d/Vagrantfile file.
config.berkshelf.enabled = true
# The path to the Berksfile to use with Vagrant Berkshelf.
# config.berkshelf.berksfile_path = './Berksfile'
# An array of symbols representing groups of cookbook described in the
# Vagrantfile to exclusively install and copy to Vagrant's shelf.
# config.berkshelf.only = []
# An array of symbols representing groups of cookbook described in the
# Vagrantfile to skip installing and copying to Vagrant's shelf.
# config.berkshelf.except = []
config.vm.provision :chef_solo do |chef|
# Set some Chef Node attributes:
chef.json = {
opendkim: {
# ...
}
}
chef.run_list = %w(
recipe[apt]
recipe[opendkim]
)
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.
#
# orgname = 'ORGNAME'
# 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