lp:~frankban/charms/precise/juju-gui/fix-charm-proof

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~juju-gui/charms/precise/juju-gui/trunk at revision 27

Juju GUI Hackers: Pending requested 2013-01-21

Diff: 35 lines (+18/-1)

2 files modified

copyright (+17/-0)
metadata.yaml (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

28. By Francesco Banconi on 2013-01-21

Fixed copyright year.

27. By Gary Poster on 2013-01-18

update charm to make "charm proof" happy

26. By Francesco Banconi on 2013-01-17

User, password and read-only options.

This branch adds three more options to
the charm. If staging is true, user and
password options are ignored, and the
authentication is automatically handled
by the charm, providing staging pre-defined
values.

R=
CC=
https://codereview.appspot.com/7127048

25. By Francesco Banconi on 2013-01-11

Juju GUI source as env var + Charm test branch

This branch introduces the possibility to provide
the Juju GUI source (used in tests) by setting an
environment variable. This way the charm tests can
be run as part of the release qa process, e.g.:

$ JUJU_GUI_SOURCE=lp:mybranch jitsu test juju-gui ...

or, to test a new trunk release:

$ JUJU_GUI_SOURCE=trunk jitsu test juju-gui ...

Also updated the test exercising the process of
making a release from a branch, i.e. when the
juju-gui-source option points to a Bazaar branch.

Now the branch used is a customized one, present in
`lp:~frankban/juju-gui/charm-tests-branch` (please
feel free to suggest another, more sane, location,
and please take a look at that as part of your reviews).
This is a test branch containing only a minimal
Makefile and a release tarball. There, `make distfile`
is almost a no-op, and for this reason the charm test
speed is slightly increased (~4 minutes on ec2).
Source: http://bazaar.launchpad.net/~frankban/juju-gui/charm-tests-branch/files

R=gary.poster, teknico
CC=
https://codereview.appspot.com/7102044

24. By Nicola Larosa on 2013-01-11

Update the README and HACKING docs

Update the README.md and HACKING.md docs to reflect the current
status. Add to the former a section and link to the demo/staging
server (https://uistage.jujucharms.com:8080/).

R=gary.poster, frankban
CC=
https://codereview.appspot.com/7103043

23. By Francesco Banconi on 2013-01-11

Implemented Selenium tests and login-help.

This branch introduces integration tests based
on Selenium. This way it is possible to check that
the GUI actually works, is connected to the API
backend, etc.

Firefox is the webdriver used here, it is installed
by default in Ubuntu. All the graphical operations
are executed in memory thanks to xvfbwrapper.

This branch also includes the changes Gary made to
add a charm option for the login help text.

R=gary.poster, teknico
CC=
https://codereview.appspot.com/7064068

22. By Gary Poster on 2013-01-10

Make charm work without environment Juju PPA

As discovered by therve and myself, the charm does not work if "juju-origin: ppa" is not in your environments.yaml for the given Juju environment. These changes work around the problem.

R=matthew.scott, frankban
CC=
https://codereview.appspot.com/7073051

21. By Nicola Larosa on 2013-01-04

Setup encrypted conn. to the API environment

Pass the same certificate and private key used by nginx to the
API environment, so that the websocket connection can use WSS.

R=frankban, gary.poster
CC=
https://codereview.appspot.com/7007045

20. By Francesco Banconi on 2013-01-03

Restore TLS in the charm

Now the charm is served using SSL again.

R=teknico, hazmat
CC=
https://codereview.appspot.com/7026046

19. By Francesco Banconi on 2012-12-22

Allow using an own SSL cert and private key.

Added two new config options, one for the certificate, one
for the private key. If they are both provided, they are used
by nginx, otherwise, a new certificate is automatically
generated.

Fixed a pre-existent bug: even if you can specify the
directory where to store the certificates, this path
was not used by nginx, because an hardcoded one was
present in the configuration file.

Improved how ssl options are handled in config-changes.
If the SSL path is changed using 'juju set', now that
change is reflected in the nginx config file, and the
service correctly restarted.

Added tests for the process of saving or generating SSL
certificates.

Some code clean up.

Please note that all the SSL stuff is still
disabled/commented.

R=teknico, matthew.scott, gary.poster
CC=
https://codereview.appspot.com/6976046