lp:~benji/charms/precise/juju-gui/make-etags-ignore-inode

Branch merges

Propose for merging

No branches dependent on this one.

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

charmers: Pending requested 2014-01-21

Diff: 16 lines (+2/-0)

1 file modified

config/apache-site.template (+2/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

150. By Benji York on 2014-01-21

add etag config that excludes inode from the hash, making etags from different back-end servers match one another

149. By Richard Harding on 2014-01-16

Change juju-gui-source to be git-enabled.

- Allow pulling from various repo urls
- Support checking out a branch name
- Support checkout out a direct sha
- Remove support for the trunk releases.

The list of what you can check out is simplified a bit. You can easily use the
git access, url, or a local file in the releases directory to enable loading
the gui with any combination of code you would like to use.

Drive by removing some left over bits of the PyJuju branch previously.

148. By Richard Harding on 2014-01-15

Remove support for PyJuju and rapi from charm.

- Removes the support for running rapi/pyjuju.
- Removes the agent used to communicate with zookeeper.
- Removes anything pertaining to zookeeper.
- Attempts to clean up docs and such to make sense with pure juju-core.

147. By Richard Harding on 2014-01-13

Pull upstream changes

146. By Richard Harding on 2014-01-13

Remove existing Log handers when setupLogging.

145. By Francesco Banconi on 2013-12-05

Merged back the new charm release.

144. By Francesco Banconi on 2013-12-05

Updated to the newest juju-gui release.

143. By Francesco Banconi on 2013-12-05

Merged changes from the released charm.

142. By Francesco Banconi on 2013-11-28

Deploy the GUI to machine 0 in functional tests.

Also added guiserver info checks, and fixed the
deploy module so that the previous behavior of
"make deploy" is restored and the resulting
service name is not random generated.

Removed test_local_release: that scenario is
already tested in TestBuiltinServerLocalRelease.

Moved test_nrpe_check_available to
TestBuiltinServerLocalRelease.

Tests: assuming ec2 is the name of your ec2
environment, run the following:
`time make ftest JUJU_ENV="ec2"`
Tests should pass and take ~25-30 minutes.

R=gary.poster, matthew.scott, jeff.pihach
CC=
https://codereview.appspot.com/34130043

141. By Brad Crittenden on 2013-11-27

Extract the message from EnvError on deploy err.

R=gary.poster
CC=
https://codereview.appspot.com/34270044