- 1 Why use a demo browser?
- 2 Claiming a demo browser
- 3 What about htdocs?
- 4 Building your demo CGIs
- 5 Building trackDb_demoN
- 6 Viewing your demo
- 7 Your demo responsibility
- 8 Problems? Additions?
Why use a demo browser?
Frequently it is desirable to demonstrate browser features that are not yet ready to be pushed into the git master branch and/or not ready to be introduced into the genome-test (hgwdev) browser. This is especially so for large or experimental features that QA may need to test drive before they are approved to be put into the three week CGI release cycle. Alternatively, you may wish to demonstrate a track organization as represented in trackDb, but you can't build this trackDb into alpha yet. Keeping these features static in your own sandbox is the simplest solution. However, that is not always practical as we all have many things to work on. To help you there are 9 demo sandboxes cleverly named: demo1 through demo9.
Additionally, as of Summer 2020, each Browser engineer has a per-developer virtual host named: hgwdev-demo-$USER. These can be used by the $USER for branch or development work and are not bound by the claiming system described below.
Claiming a demo browser
The demo browsers are sandboxes like your own and the cgis live on hgwdev in the appropriate cgi-bin directory:
To claim one, you should first see that no one else has that demo directory by seeing who owns the CGIs in that directory and how old they are:
ll /usr/local/apache/cgi-bin-demo2/ -rwxrwxr-x 1 tdreszer protein 11954236 Sep 15 2010 hgTracks ...
If the CGIs in a demo cgi-bin are more than a couple months old, then that demo browser can be considered fair game. If there is any doubt, ask the owner.
Here is a list of current claims, but it is no doubt out of date as you read this:
Claimed sandbox table
|demo2||max||2018-01-29||cairo drawing engine|
|demo3||galt||2019-01-21||save and restore CTs to current session|
|demo4||chris||2020-04-16||phased trio display|
|demo5||kate||2020-02-21||featured track sessions #25601|
|demo6||max||2019-08-12||UI interface changes: composites and hgTracks boxes|
|demo8||Hiram||2019-01-04||staAur2 genome browser|
What about htdocs?
Building your demo CGIs
Just like the default make targets in any other sandbox, the demo dirs are built based upon the value of USER in the make environment.
Method 1: add USER=demoN to make commands
You can set the value of any variable in the make environment on the command line like this:
cd ~/kent/src/hg make cgi USER=demo2
Method 2: modify your shell variable $USER
If you find yourself forgetting to add USER=demoN too often, you can set your shell environment's USER to "demo2" (or whatever demo you have claimed) and then make your CGIs with the same make command as usual. It's a good idea to do this in a shell/window that you will use only for demo building.
export USER=demo2;echo $USER # bash syntax setenv USER demo2 # tcsh syntax cd ~/kent/src/hg/ make cgi
rsync errors for cgi-bin-demoN/hg*Data
When you rebuild all CGIs on demoN, you might be halted by rsync errors if cgi-bin-demoN/hgNearData and hgGeneData files are owned by the previous demo developer (rsync attempts to chgrp and fails). If you do, just rm them and re-run your make.
rm -r /usr/local/apache/cgi-bin-demo2/hgGeneData /usr/local/apache/cgi-bin-demo2/hgNearData
All sandboxes have their own htdocs:
cd ~/kent/src/hg/htdocs make USER=demo2 cd ~/kent/src/hg/htdocs/style make USER=demo2 cd ~/kent/src/hg/js make USER=demo2
Do you need to do a full make (make clean;make...)? It is a good idea, but you are running in the context of your current git branch. If your src/lib and src/hg/lib have already been made, then you only need to assure the CGIs and possibly htdocs get rebuilt. Especially when you are first claiming the demo sandbox, I recommend a full make.
Just like with your own sandbox, there is a trackDb_demo# for each assembly which will probably be well out of date when you claim a demo sandbox. Chances are that you only need to demo a new feature on one assembly however, so you can just rebuild that assembly as the demo user:
cd ~/kent/src/hg/makeDb/trackDb make DBS=hg19 USER=demo2
Nothing is preventing you from making all assembles as the demo user. It is your time!
Remember: If you modified your USER environment variable (Method 2 above), when you are done building demoN, set USER back to yourself!
export USER=$(whoami); echo $USER # bash syntax setenv USER `whoami` # tcsh syntax
Viewing your demo
This is just another sandbox, so view it like you view your own:
https://hgwdev-demo1.gi.ucsc.edu https://hgwdev-demo2.gi.ucsc.edu https://hgwdev-demo3.gi.ucsc.edu https://hgwdev-demo4.gi.ucsc.edu https://hgwdev-demo5.gi.ucsc.edu https://hgwdev-demo6.gi.ucsc.edu https://hgwdev-demo7.gi.ucsc.edu https://hgwdev-demo8.gi.ucsc.edu https://hgwdev-demo9.gi.ucsc.edu
Remember: Make sure to have your own copy of hg.conf (edited to replace <yourname> with <yourdemo>) in the /usr/local/apache/cgi-bin-demoN directory.
Your demo responsibility
- Since you are reading this document, go ahead and update the table above, when you claim a demo sandbox.
- You are responsible for advertising the features you have made available in a demo browser.
- It is your responsibility to make sure all the CGIs necessary are working. If the feature you added is in the "hgc" CGI but you didn't bring "hgTracks" up to date, then don't be surprised if someone in your target audience thinks your new feature has created a mess and broken the browser in ways entirely unrelated to what you actually coded.
- Likewise, it is your responsibility to see that all the assemblies necessary are working. If QA wants to test your feature on a mouse assembly then don't cause them irritation by leaving the mouse trackDb_demoN in some year old state.
- Finally, you can get out of the way when you are done with a demo browser. Perhaps you should just delete out the CGIs which will make it obvious that you are done with it. And if you are really responsible, you will update the claimed sandbox table above.
If these instructions are lacking or if you find and resolve problems with this documentation, please extend or correct it.