lp://staging/~dpb/charms/precise/haproxy/trunk

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/charms/haproxy at revision 67

Mark Mims (community): Approve on 2013-06-03

Diff: 12 lines (+1/-1)

1 file modified

hooks/hooks.py (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

74. By David Britton on 2014-01-20

merging in current fix branch for testing

73. By David Britton on 2014-01-20

Merging in trunk, taking other

72. By David Britton on 2013-09-17

Merging in jseutter errorfiles-2 branch. Allows charms to specify error files
to be used for standard http error codes when forming relations with haproxy.

Merged branch lp://staging/~jseutter/charms/precise/haproxy/errorfiles-2

71. By David Britton on 2013-07-22

- Add tests for website_notify
- Add check that multiple relations work the same as one
- realign test data to be the same numbers

70. By David Britton on 2013-07-22

update revision

69. By David Britton on 2013-07-22

clean up docstring a bit to reveal intent of website-notify method

68. By David Britton on 2013-07-22

actually inform website relation of data change, not just a time update

67. By Mark Mims on 2013-06-03

merging lp:~davidpbritton/charms/precise/haproxy/trunk

66. By Jorge Castro on 2013-04-22

Add categories.

65. By Juan L. Negron on 2013-02-15

When the reverseproxy relation changes, the website proxy will likely need to be updated, so trigger a config-changed to notify the other side of the relation that it will need to update.

I'm not sure if this the appropriate way to handle this situation, but in practice it seems to work. Please let me know if there is a more accurate or correct way to do it. LP:148605