BMO/DeveloperBox: Difference between revisions

← Older edit

BMO/DeveloperBox (view source)

Revision as of 21:50, 6 November 2015

98 bytes added , 6 November 2015

no edit summary

DaveLawrence

766

edits

@@ Line 1: / Line 1: @@
-=== Creating a BMO Development System using VirtualBox and Vagrant ===
+== Creating a BMO Development System using Docker ==
-* Install Virtualbox on your workstation (http://www.virtualbox.org)
+Getting Bugzilla, as well as the latest code that is used by [http://bugzilla.mozilla.org bugzilla.mozilla.org], installed and running locally in order to
-* Install Vagrant on your workstation (http://www.vagrantup.com/)
+make changes, fix bugs, etc. is not the easiest thing for every one to do. Especially if you are not familiar with Linux systems, the Perl programming
-* Creating your VM from the BMO base vbox
+language, or installing all of the many CPAN module dependencies needed for Bugzilla to work properly. This Developer Box is designed to help people
-** Note: ~7G download (the base vbox has a recent sanitized copy of BMO)
+to be able to get up and running quickly and easily by providing a ready to run Docker container that should work on most platforms.
-  vagrant init
-  vagrant box add bmo https://people.mozilla.com/~dkl/bugzilla.box
+First you will need to check the latest BMO source code from https://git.mozilla.org/webtools/bmo/bugzilla into a local directory and change into the
-* Edit Vagrantfile to allow port forward to VM of port 80
+contrib/docker directory.
-** TODO: Figure out what needs to be done to have this in the base vbox instead
-of requiring user to do it.
+   $ git clone https://git.mozilla.org/webtools/bmo/bugzilla.git docker-bugzilla
-   Uncomment the line that says:
+   $ cd docker-bugzilla/docker
-  # config.vm.forward_port 80, 8080
-* Starting the VM
+For instructions on how to get your platform setup to run Docker as well as information on how to start the container, see the [https://github.com/mozilla/webtools-bmo-bugzilla/blob/master/docker/README.md README.md] file in the current directory.
-  vagrant up
-* Logging into the VM
-  vagrant ssh
-* Access the web UI at http://localhost:8080/bmo using your browser
-* Updating the BZR code to the latest revision
-  vagrant ssh
-   cd htdocs/bmo
-  bzr merge
-* Making a patch fore review of your latest changes
-** 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