-
Notifications
You must be signed in to change notification settings - Fork 0
/
Vagrantfile
94 lines (81 loc) · 3.69 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
# -*- 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://vagrantcloud.com/search.
#
# the holochain-vagrant box is generated by running:
# nix-shell --run hc-test
# from inside the /vagrant dir, which prewarms nix, rust and npm
config.vm.box = "holochain-vagrant"
config.vm.box_url = "https://holochain.love/box"
# uncomment this to use the raw nixos base box instead of the holochain box
# config.vm.box = "nixos/nixos-18.03-x86_64"
# 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.
# NOTE: This will enable public access to the opened port
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine and only allow access
# via 127.0.0.1 to disable public access
# config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
# 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 = false
# Customize the amount of memory on the VM:
vb.memory = "4096"
vb.cpus = "4"
vb.customize ["modifyvm", :id, "--hwvirtex", "off"]
end
# View the documentation for the provider you are using for more
# information on available options.
# requires the vagrant-nixos-plugin to work
# `vagrant plugin install vagrant-nixos-plugin`
# add some simple dev tools
# add some swap space to allow for more RAM on small devices
config.vm.provision :nixos,
run: 'always',
expression: {
swapDevices: [ { device: "/swapfile", size: 16384 } ],
environment: {
systemPackages: [
# htop is handy for diagnosing runaway memory and cpu usage
:htop,
# sometimes windows can mess with line endings
# dos2unix can fix that inside the box
# mostly a debugging tool, ultimately the correct line endings need to
# be committed
:dos2unix,
:vim
]
}
}
end