|
|
| (25 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| This page is for developers, it's not relevant for QA. | | This page is no longer maintained. |
|
| |
|
| Development can happen on the devbox, a development version of the browserbox with git, gcc etc. For testing during development, a special command on the box can pull in the CGIs that were compiled on the devbox.
| | See http://genomewiki.ucsc.edu/genecats/index.php/Gbib_development |
| | |
| You can start and stop browserbox-dev with the aliases devStart and devStop. Browserbox-dev listens at 1236 for web requests and at 1237 for ssh.
| |
| | |
| All virtual machines live in qateam/VirtualBox VMs/. The central virtualbox xml config file where they are registered is ~/.config/VirtualBox/VirtualBox.xml
| |
| | |
| start browserbox-dev:
| |
| devStart
| |
| | |
| connect + git pull + compile:
| |
| ssh devbox
| |
| compileCgis
| |
| | |
| You can now test the CGIs on port 1236 of hgwdev. You can also hack on the /home/browser/kent directory and e.g. run makes in there.
| |
| | |
| To do a more realistic test, the alpha binaries can also be put into the final browserbox.
| |
| | |
| To copy the alpha binaries into the browserbox: Copy them from devbox to alpha distribution rsync server directory (this command is defined in qateam's .bashrc) by running this command as qateam:
| |
| boxUpdateAlpha
| |
| | |
| Now start the box and pull the alpha binaries from the rsync server:
| |
| boxStart
| |
| ssh box
| |
| updateBrowser alpha
| |
| | |
| You can now use the alpha CGIs on port 1234 of hgwdev.
| |
| | |
| When you're done: stop the development box:
| |
| devStop
| |
Latest revision as of 11:44, 21 August 2018
