BMO/DeveloperBox: Difference between revisions
< BMO
Jump to navigation
Jump to search
Line 47: | Line 47: | ||
so you can easily upload, etc. | so you can easily upload, etc. | ||
bzr diff > /vagrant/<some_patch_name>_1.patch | bzr diff > /vagrant/<some_patch_name>_1.patch | ||
* File any bugs or feature requests [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Developer%20Box here] |
Revision as of 22:03, 25 November 2013
Creating a BMO Development System using VirtualBox and Vagrant
- Install Virtualbox on your workstation (http://www.virtualbox.org)
- Install Vagrant on your workstation (http://www.vagrantup.com/)
- Creating your VM from the BMO base vbox
- Note: ~7G download (the base vbox has a recent sanitized copy of BMO)
vagrant init vagrant box add bmo https://people.mozilla.com/~dkl/latest.box
- Edit Vagrantfile to allow port forward to VM of port 80
- TODO: Figure out what needs to be done to have this in the base vbox instead
of requiring user to do it.
Uncomment the line that says (according to version): Version 1.0.x: # config.vm.forward_port 80, 8080 Version 1.1.x: # config.vm.network :forwarded_port, guest: 80, host: 8080
In the line config.vm.box = "base" Change "base" to "bmo"
- Starting the VM
vagrant up
- Logging into the VM
vagrant ssh
- Make yourself an admin and set your password (substitute your bmo address below)
vagrant ssh cd htdocs/bmo ./checksetup.pl --make-admin=<email> --reset-password=<email>
- Access the web UI at http://localhost:8080/bmo using your browser
- You may need to update the values for urlbase and sslbase in /home/vagrant/htdocs/bmo/data/params to match the port number you chose for redirection earlier. If the port is different than 8080.
- Updating the BZR code to the latest revision. Note: http://doc.bazaar.canonical.com/migration/en/survival/bzr-for-git-users.html
vagrant ssh cd htdocs/bmo bzr merge bzr commit (commit the merged files to your branch?)
- Run tests.
- perl runtests.pl will run all the tests in the /bmo/t directory
- you can run just one of the tests in /t, for example, perl t/004template.t will go through all the template tests.
- Making a patch for review of your latest changes
- (see https://wiki.mozilla.org/Bugzilla:Patches)
- This will place the patch file in your home directory of the laptop and not on the VM
so you can easily upload, etc.
bzr diff > /vagrant/<some_patch_name>_1.patch
- File any bugs or feature requests here