Difference between revisions of "WOCE Build Environment"
BigBlueHat (talk | contribs) |
m (formatting) |
||
| Line 1: | Line 1: | ||
<big>Develop in your environment, Build in ours. </big> | <big>Develop in your environment, Build in ours. </big> | ||
| − | |||
== WOCE Build Environment == | == WOCE Build Environment == | ||
| − | |||
===Introduction=== | ===Introduction=== | ||
| Line 33: | Line 31: | ||
5. From a Command Prompt in the directory you have set aside for your woce-be VM | 5. From a Command Prompt in the directory you have set aside for your woce-be VM | ||
| − | + | vagrant box add woce-be <nowiki>http://bit.ly/QS3G1p</nowiki> | |
| − | + | vagrant init woce-be | |
| − | + | vagrant up | |
| − | |||
| − | |||
====OSX Setup==== | ====OSX Setup==== | ||
| Line 66: | Line 62: | ||
sudo nfsd enable | sudo nfsd enable | ||
| − | |||
sudo nfsd checkexports | sudo nfsd checkexports | ||
| − | |||
showmount -e | showmount -e | ||
| Line 80: | Line 74: | ||
2. Edit: | 2. Edit: | ||
/etc/exports | /etc/exports | ||
| − | + | ''(requires superuser)'' | |
3. Add the following to the end: | 3. Add the following to the end: | ||
| Line 123: | Line 117: | ||
4. Save and close the fstab | 4. Save and close the fstab | ||
| − | 5 run the following command: | + | 5. run the following command: |
sudo mount /srv/share | sudo mount /srv/share | ||
''(Subject to change if using the host's WOCE folder)'' | ''(Subject to change if using the host's WOCE folder)'' | ||
Revision as of 15:23, 3 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 your woce-be VM
vagrant box add woce-be http://bit.ly/QS3G1p vagrant init woce-be vagrant up
OSX Setup
1. Edit:
/System/Library/LaunchDaemons/com.apple.nfsd.plist
(requires superuser)
2. Scroll down to the line that reads:
<string>/sbin/nfsd</string>
3. Add a new line below it that reads:
<string>-N</string>
4. Save the file, close it
5. Edit:
/etc/exports
(requires superuser)
6. Add the following:
/path/to/shared/dir -mapall=501
7. Save and close it
8. Open Terminal.app and run the following:
sudo nfsd enable sudo nfsd checkexports showmount -e
If successful, your share's path should be printed to stdout.
Ubuntu Setup
1. Install NFS Server
sudo apt-get install nfs-kernel-server
2. Edit:
/etc/exports
(requires superuser)
3. Add the following to the end:
/PATH/TO/HOST/SHARE 127.0.0.1(rw,sync,insecure,no_root_squash)
4. Save and close /etc/exports
5. Run the following command:
sudo nfs-kernel-server restart
Arch Linux Setup
1. Install NFS Server
sudo pacman -S nfs-utils
2. Edit:
/etc/exports (requires superuser)
3. Add the following to the end:
/PATH/TO/HOST/SHARE 127.0.0.1(rw,sync,insecure,no_root_squash)
4. Save and close /etc/exports
5. Run the following commands in this order:
rc.d start rpcbind (or: rc.d start portmap) rc.d start nfs-common (or: rc.d start nfslock) rc.d start nfs-server (or: rc.d start nfsd)
Client Setup
1. Connect to VM
vagrant ssh
2. Edit:
/etc/fstab
3. Modify the bottom line, replacing (requires super user):
/PATH/TO/HOST/SHARE
with the location of woce-build clone on your host machine
4. Save and close the fstab
5. run the following command:
sudo mount /srv/share
(Subject to change if using the host's WOCE folder)