Skip to content

Commit

Permalink
Updated bugs in initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
babrodtk committed Apr 9, 2015
1 parent a6925c0 commit e6e1f8a
Show file tree
Hide file tree
Showing 3 changed files with 19 additions and 7 deletions.
22 changes: 17 additions & 5 deletions vagrant/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,24 +3,22 @@ Vagrant

[Vagrant](www.vagrantup.com) is a tool for creating and configuring reproducible and
portable development environments. It essentially creates a (disposable) virtual machine
for you that sets up OPM automatically. The files in this directory is everything you need
for you that can set up OPM automatically. The files in this directory is everything you need
to create a Ubuntu 14.04 environment that checks out, compiles, and tests OPM modules.

It requires [VirtualBox](www.virtualbox.org) and Vagrant to be installed.
They are apt-gettable on recent Ubuntus and have relatively hassle-free installers
on Windows and OSX.


To use vagrant execute the following from the directory containting the ```VagrantFile```.
```
$ sudo apt-get install vagrant
$ vagrant up
```

The first time this is executed will take a significant amount of time, as the full Ubuntu
image must be downloaded. Consequently, OPM will be downloaded (from github), compiled,
and tests run. After this process has completed, you can log into the machine and try out
OPM.
image must be downloaded. After this process has completed, you can log into the machine
and try out OPM.

Execute the following to log into the virtual machine as the vagrant user
```
Expand All @@ -30,3 +28,17 @@ $ vagrant ssh
From here you can build and execute tests in a reproducible environment. Everything you do
in this environment can easily be discarded, and will only affect the virtual machine:
your own machine will remain unaffected by changes here.

To clone, compile, and test OPM, simply run the shell script
```
vagrant@vagrant$ /host/clone_and_compile.sh
```
*inside* the virtual machine (after executing ```vagrant ssh```). This takes quite some time
to download, compile, and test the OPM modules one by one.

If you for some reason are unhappy with the virtual machine, you can dispose of it easily
by executing
```
$ vagrant destroy
```
from outside the virtual machine.
2 changes: 1 addition & 1 deletion vagrant/Vagrantfile
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# 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 "..", "/opm-host"
config.vm.synced_folder ".", "/host"

# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
Expand Down
2 changes: 1 addition & 1 deletion vagrant/bootstrap.sh
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
#!/usr/bin/env bash

./install_packages.sh
/host/install_packages.sh

0 comments on commit e6e1f8a

Please sign in to comment.