Docs update for running behind a firewall

Docs update for running behind a firewall

Also includes a driveby on 'staging' info.

https://code.launchpad.net/~makyo/charms/precise/juju-gui/docs-source/+merge/177653

(do not edit description out of merge proposal)

[matthew.scott, 2013-07-30 17:13:38]

Please take a look.

[gary.poster, 2013-07-30 19:09:10]

LGTM. Thank you very much for doing this.  I made some additions.  Please
review, change as desired, and land.  Thank you.

Please qa that the markdown looks ok.  I did not.

When you land, please make this change first to the ~juju-gui-charmers branch,
and then merge that branch into the ~juju-gui branch.

Gary

https://codereview.appspot.com/12120043/diff/1/README.md
File README.md (right):

https://codereview.appspot.com/12120043/diff/1/README.md#newcode81
README.md:81: This charm pulls the latest release from the Juju GUI page on
Launchpad.  If you
While we may change this in the future to make firewall deploys simpler, this
charm pulls the latest release...

https://codereview.appspot.com/12120043/diff/1/README.md#newcode83
README.md:83: you can configure the charm to pull the GUI release from a
location you specify.
...to pull the necessary sources from a location you specify.

For both Juju Core, you must simply do the following steps.  Note that PyJuju
must do these steps, plus another set described further below.

The config variable `juju-gui-source`...

https://codereview.appspot.com/12120043/diff/1/README.md#newcode85
README.md:85: both `http://` and `file://` protocols.
We will use this to load a local copy of the GUI source.

https://codereview.appspot.com/12120043/diff/1/README.md#newcode89
README.md:89: location that will be accessible to the *unit* either via
filesystem or HTTP.
...via filesystem (on the unit on which the GUI is running) or HTTP.

https://codereview.appspot.com/12120043/diff/1/README.md#newcode101
README.md:101: `juju resolved --retry juju-gui/0`
These steps are sufficient for Juju Core.  If you are using PyJuju, you need to
do another set of steps in addition.

1. Use bzr to branch lp:~hazmat/juju/rapi-rollup locally ("bzr branch
lp:~hazmat/juju/rapi-rollup") and copy the branch to the gui service machine.

2. Use "juju set juju-gui juju-api-branch=PATH_TO_LOCAL_BZR_BRANCH" (where the
path is *not* a file:// URI).

3. Retry as described in the step 3 above (`juju resolved --retry juju-gui/0`).