Difference between revisions of "WOCE Build Environment"
ShiftyAxel (talk | contribs) |
ShiftyAxel (talk | contribs) |
||
| Line 46: | Line 46: | ||
From here, there will be a woce-build directory in /vagrant/home. | From here, there will be a woce-build directory in /vagrant/home. | ||
| − | And when you're done: | + | And when you're done: |
| − | |||
'''Shut down the VM''' | '''Shut down the VM''' | ||
vagrant destroy | vagrant destroy | ||
Revision as of 21:31, 5 July 2012
Develop in your environment, Build in ours.
WOCE Build Environment
Introduction
The WOCE BE uses Vagrant and Virtualbox to create a self-contained build environment for use on OSX and Linux Hosts.
Our goal is to create a consistent build setup for developers so that if there are issues with builds we can know that we all are singing off the same sheet of music.
Minimum Requirements
x86 based computer running OSX(10.5 minimum) or Linux(32bit or 64bit).
Enough resources to allot:
- 1 "Virtual CPU"
- 1GB "Virtual RAM"
- 20GB "Virtual HD"
Installation Procedure
1. From your development host go to Vagrant Downloads and download the latest version for your host.
2. From your development host go to Virtualbox Downloads and download the latest version for your host.
3. Install Virtualbox
4. Install Vagrant (Vagrant Getting Started Guide)
5. From a Command Prompt in the directory you have set aside for the build environment
git clone git://www.github.com/woce/woce-be
Usage
From a Command Prompt in the woce-be directory:
Bring the VM online
vagrant up
(You can ignore stdin: not a tty errors- these are normal)
SSH into the VM
vagrant ssh
From here, there will be a woce-build directory in /vagrant/home.
And when you're done: Shut down the VM
vagrant destroy