# Juju GUI Charm #
This charm makes it easy to deploy a Juju GUI into an existing environment.
## Supported Browsers ##
The Juju GUI supports recent releases of Chrome and Chromium. Recent Firefox
releases are also supported, but regressions may occur until the completion of
upcoming continuous integration work.
## Demo/Staging Server ##
A [demo/staging server](https://uistage.jujucharms.com:8080/) is available.
## Deploying the Juju GUI ##
Deploying the Juju GUI is accomplished using Juju itself.
You need a configured and bootstrapped Juju environment: see the Juju docs
about [getting started](https://juju.ubuntu.com/docs/getting-started.html),
and then run the usual bootstrap command.
Next, you simply need to deploy the charm and expose it. (See also "Deploying
with Jitsu" below, for another option.)
juju deploy juju-gui
juju expose juju-gui
Finally, you need to identify the GUI's URL. It can take a few minutes for the
GUI to be built and to start; this command will let you see when it is ready
to go by giving you regular status updates:
watch juju status
Eventually, at the end of the status you will see something that looks like
That tells me I can go to the public-address in my browser via HTTPS
(https://ec2-www-xxx-yyy-zzz.compute-1.amazonaws.com/ in this example), and
start configuring the rest of Juju with the GUI. You should see a similar
web address. Accessing the GUI via HTTP will redirect to using HTTPS.
By default, the deployment uses self-signed certificates. The browser will ask
you to accept a security exception once.
You will see a login form with the username fixed to "admin". The password is
the same as your Juju environment's `admin-secret`, found in
### Deploying with Jitsu ###
The instructions above cause you to use a separate machine to work with the
GUI. If you'd like to reduce your machine footprint (and perhaps your costs),
you can colocate the GUI with the Juju bootstrap node. This approach will
change in the future (probably with the Juju shipped with Ubuntu 13.04), so be
For now, though, install Jitsu...
sudo apt-get install juju-jitsu
...and then replace "juju deploy juju-gui" from the
previous instructions with this:
jitsu deploy-to 0 juju-gui
## Contacting the Developers ##
If you run into problems with the charm, please feel free to contact us on the
[Juju mailing list](https://lists.ubuntu.com/mailman/listinfo/juju), or on
Freenode's IRC network on #juju. We're not always around (working hours in
Europe and North America are your best bets), but if you send us a mail or
ping "jujugui" we will eventually get back to you.
If you want to help develop the charm, please see the charm's `HACKING.md`.
|2013/05/17 Francesco Banconi Support juju-gui-source=branch:revno
Added support for creating and deploying
a release from a spec (revno 58)
|2013/05/03 Nicola Larosa More charm code cleanup.
Most of these changes were split from the former branch that added
backend (revno 57)
|2013/05/03 Francesco Banconi Fix import errors in stop hook.
This branch includes three trivial fixes:
- stop hook not working;
|2013/05/02 Nicola Larosa Add more unit tests to the charm backend.
More unit tests for backend properties, commands and meth (revno 55)
|2013/05/02 Nicola Larosa Reinstate test symbolic links.
Actually reinstate test symbolic links that were mistakenly
replaced (revno 54)
|2013/04/30 Benji York add missing parameter (revno 53)
|2013/04/30 Benji York fix accedentally removed symlinks (revno 52)
|2013/04/30 Benji York Use the npm cache to speed installs from a branch
Creating the cache is handled by the GUI Makefile (revno 51)
|2013/04/30 Kapil Thangavelu read only server side support (revno 50)