4 # This file is for use by Vagrant (http://www.vagrantup.com/).
5 # It will establish a debian-based (Ubuntu) virtual machine for development.
7 # The virtual machine environment attempts to match the production environment
8 # as closely as possible.
10 # This file was generated by `vagrant up` and consequently modified.
12 # Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
13 VAGRANTFILE_API_VERSION = "2"
15 # Install fabric so that the KarmaWorld fabfile may be run.
17 # build a shell script that installs prereqs, configures the database, sets up
18 # the user/group associations, pulls in the code from the host machine, and
20 shellscript = <<SCRIPT
23 apt-get install -y python-pip postgresql python-virtualenv virtualenvwrapper \
24 git nginx postgresql-server-dev-9.1 libxslt1-dev \
25 libxml2-dev libmemcached-dev python-dev rabbitmq-server
27 echo "CREATE USER vagrant WITH CREATEROLE LOGIN; CREATE DATABASE karmaworld OWNER vagrant;" | su postgres -c "psql"
29 mkdir -m 775 -p /var/www
30 chown -R :www-data /var/www
31 usermod -a -G www-data vagrant
33 su vagrant -c "git clone /vagrant karmaworld"
35 CFILE="karmaworld/karmaworld/secret/db_settings.py"
39 # Copyright (C) 2012 FinalsClub Foundation
41 DO NOT check this file into source control.
43 PROD_DB_NAME = 'karmaworld'
44 PROD_DB_USERNAME = 'vagrant'
47 chown vagrant:vagrant $CFILE
50 #su vagrant -c "cd karmaworld; fab here first_deploy"
54 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
55 # All Vagrant configuration is done here. The most common configuration
56 # options are documented and commented below. For a complete reference,
57 # please see the online documentation at vagrantup.com.
59 # Every Vagrant virtual environment requires a box to build off of.
60 config.vm.box = "Official Ubuntu 12.04 daily Cloud Image i386"
61 #config.vm.box = "Official Ubuntu 12.04 daily Cloud Image amd64"
62 #config.vm.box = "Official Ubuntu 12.10 daily Cloud Image i386"
63 #config.vm.box = "Official Ubuntu 12.10 daily Cloud Image amd64"
64 #config.vm.box = "Official Ubuntu 13.04 daily Cloud Image i386"
65 #config.vm.box = "Official Ubuntu 13.04 daily Cloud Image amd64"
66 #config.vm.box = "Official Ubuntu 13.10 daily Cloud Image i386"
67 #config.vm.box = "Official Ubuntu 13.10 daily Cloud Image amd64"
69 # The url from where the 'config.vm.box' box will be fetched if it
70 # doesn't already exist on the user's system.
71 config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-i386-vagrant-disk1.box"
72 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-amd64-vagrant-disk1.box"
73 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/quantal/current/quantal-server-cloudimg-i386-vagrant-disk1.box"
74 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/quantal/current/quantal-server-cloudimg-amd64-vagrant-disk1.box"
75 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-i386-vagrant-disk1.box"
76 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64-vagrant-disk1.box"
77 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-i386-vagrant-disk1.box"
78 #config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box"
80 # Create a forwarded port mapping which allows access to a specific port
81 # within the machine from a port on the host machine. In the example below,
82 # accessing "localhost:8080" will access port 80 on the guest machine.
83 # config.vm.network :forwarded_port, guest: 80, host: 8080
85 # OM (sanskrit) KW (KarmaWorld) on a phone: 66 59
86 config.vm.network :forwarded_port, guest: 80, host: 6659, auto_correct: true
88 # Create a private network, which allows host-only access to the machine
89 # using a specific IP.
90 #config.vm.network :private_network, ip: "192.168.66.59"
92 # Create a public network, which generally matched to bridged network.
93 # Bridged networks make the machine appear as another physical device on
95 # Used to directly access the internet for downloading updates and so forth.
96 config.vm.network :public_network
98 # If true, then any SSH connections made will enable agent forwarding.
99 # Default value: false
100 # config.ssh.forward_agent = true
102 # Share an additional folder to the guest VM. The first argument is
103 # the path on the host to the actual folder. The second argument is
104 # the path on the guest to mount the folder. And the optional third
105 # argument is a set of non-required options.
106 # config.vm.synced_folder "../data", "/vagrant_data"
109 config.vm.provision "shell", inline: shellscript
111 # Provider-specific configuration so you can fine-tune various
112 # backing providers for Vagrant. These expose provider-specific options.
113 # Example for VirtualBox:
115 # config.vm.provider :virtualbox do |vb|
116 # # Don't boot with headless mode
119 # # Use VBoxManage to customize the VM. For example to change memory:
120 # vb.customize ["modifyvm", :id, "--memory", "1024"]
123 # View the documentation for the provider you're using for more
124 # information on available options.
126 # Enable provisioning with Puppet stand alone. Puppet manifests
127 # are contained in a directory path relative to this Vagrantfile.
128 # You will need to create the manifests directory and a manifest in
129 # the file base.pp in the manifests_path directory.
131 # An example Puppet manifest to provision the message of the day:
133 # # group { "puppet":
134 # # ensure => "present",
137 # # File { owner => 0, group => 0, mode => 0644 }
139 # # file { '/etc/motd':
140 # # content => "Welcome to your Vagrant-built virtual machine!
141 # # Managed by Puppet.\n"
144 # config.vm.provision :puppet do |puppet|
145 # puppet.manifests_path = "manifests"
146 # puppet.manifest_file = "site.pp"
149 # Enable provisioning with chef solo, specifying a cookbooks path, roles
150 # path, and data_bags path (all relative to this Vagrantfile), and adding
151 # some recipes and/or roles.
153 # config.vm.provision :chef_solo do |chef|
154 # chef.cookbooks_path = "../my-recipes/cookbooks"
155 # chef.roles_path = "../my-recipes/roles"
156 # chef.data_bags_path = "../my-recipes/data_bags"
157 # chef.add_recipe "mysql"
158 # chef.add_role "web"
160 # # You may also specify custom JSON attributes:
161 # chef.json = { :mysql_password => "foo" }
164 # Enable provisioning with chef server, specifying the chef server URL,
165 # and the path to the validation key (relative to this Vagrantfile).
167 # The Opscode Platform uses HTTPS. Substitute your organization for
168 # ORGNAME in the URL and validation key.
170 # If you have your own Chef Server, use the appropriate URL, which may be
171 # HTTP instead of HTTPS depending on your configuration. Also change the
172 # validation key to validation.pem.
174 # config.vm.provision :chef_client do |chef|
175 # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
176 # chef.validation_key_path = "ORGNAME-validator.pem"
179 # If you're using the Opscode platform, your validator client is
180 # ORGNAME-validator, replacing ORGNAME with your organization name.
182 # If you have your own Chef Server, the default validation client name is
183 # chef-validator, unless you changed the configuration.
185 # chef.validation_client_name = "ORGNAME-validator"