forked from lavabit/magma
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathVagrantfile
More file actions
118 lines (98 loc) · 4.55 KB
/
Vagrantfile
File metadata and controls
118 lines (98 loc) · 4.55 KB
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
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config.vm.box = "chef/centos-6.6"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# 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
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# 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"
# 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|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
#
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
#
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
config.vm.provision "shell", inline: <<-SHELL
# Enable EHEL repos (libbsd-dev)
wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
sudo rpm -ivh epel-release-6-8.noarch.rpm
# Install build dependencies
sudo yum -y install patch
sudo yum -y install autoconf
sudo yum -y install automake
sudo yum -y install libtool
sudo yum -y install check-devel
sudo yum -y install ncurses-devel # (mysql)
sudo yum -y install gcc-c++
sudo yum -y install libbsd-devel # (dkim)
sudo yum -y install git # (for generating build stamps)
# Install test dependencies
sudo yum -y install valgrind-devel
# Install runtime dependencies, start them, and configure them to start on boot
sudo yum -y install mysql-server
sudo yum -y install memcached
sudo /sbin/service mysqld start
sudo chkconfig mysqld on
sudo /sbin/service memcached start
sudo chkconfig memcached on
# The VM will be low on entropy when we start it. This will cause magma to
# hang waiting for /dev/random. We'll use haveged to generate more entropy.
sudo yum -y install haveged
sudo /sbin/service haveged start
sudo chkconfig haveged on
# Make sure we're in the source directory
cd /vagrant
# Set up database
# Note that this will currently overwrite some sql files under version control
./scripts/database/schema.init.sh root "" Lavabit
# Set up sandbox config
cp res/config/magma.sandbox.config.vagrant res/config/magma.sandbox.config
# Make directory needed for tests
sudo -u vagrant mkdir -p /home/vagrant/spool/data
# Fix permissions warnings
chmod 600 res/config/localhost.localdomain.pem
chmod 600 res/config/dkim.localhost.localdomain.pem
# Change memlock limits for mmap
echo "* hard memlock unlimited" | sudo tee -a /etc/security/limits.conf
echo "* soft memlock unlimited" | sudo tee -a /etc/security/limits.conf
SHELL
end