-
Notifications
You must be signed in to change notification settings - Fork 7
/
Vagrantfile.production
82 lines (73 loc) · 3.49 KB
/
Vagrantfile.production
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
# -*- 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.
# Use vagrant-wheezy64 if you want to rebuild entirely ruby, svn
# Use markus-wheezy64 if you want a ready-to-use virtual machine
# If you don't know exactly what you're doing, prefer markus-wheezy64
config.vm.box = "vagrant-wheezy64"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
# Use vagrant-wheezy64 if you want to rebuild entirely ruby, svn
# Use markus-wheezy64 if you want a ready-to-use virtual machine
config.vm.box_url = "http://www.markusproject.org/download/vagrant-wheezy64.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, 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", "../data"
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
config.vm.provision :chef_solo do |chef|
chef.cookbooks_path = "cookbooks"
chef.roles_path = "roles"
chef.data_bags_path = "data_bags"
chef.add_recipe "chef-solo-search"
chef.add_recipe "htop"
chef.add_recipe "vim"
chef.add_recipe "ruby_build"
chef.add_recipe "database::postgresql"
chef.add_recipe "postgresql::default"
chef.add_recipe "postgresql::client"
chef.add_recipe "postgresql::server"
chef.add_recipe "postgresql::server_debian"
chef.add_recipe "unicorn::default"
chef.add_recipe "nginx::default"
chef.add_recipe "users::root"
chef.add_recipe "users::vagrant"
chef.add_recipe "users::markus"
chef.add_recipe "bash"
chef.add_recipe "openssh::default"
chef.add_recipe "subversion::source"
chef.add_recipe "markus::production"
chef.add_recipe "markus::ldap"
chef.json = { :postgresql => { :password => { :postgres => "vagrant" }}}
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
end
end