Merge lp://staging/~marcoceppi/charms/precise/wordpress/apache-dog-pile into lp://staging/charms/wordpress
Status: | Merged |
---|---|
Approved by: | Mark Mims |
Approved revision: | 81 |
Merged at revision: | 61 |
Proposed branch: | lp://staging/~marcoceppi/charms/precise/wordpress/apache-dog-pile |
Merge into: | lp://staging/charms/wordpress |
Diff against target: |
828 lines (+392/-155) 16 files modified
README.md (+19/-1) config.yaml (+8/-14) files/charm/apache/etc_apache2_conf-d_php5-fpm.conf (+6/-0) files/charm/apache/etc_apache2_sites-enabled_loadbalancer (+21/-0) files/charm/apache/etc_apache2_sites-enabled_wordpress (+20/-0) hooks/config-changed (+107/-3) hooks/db-relation-changed (+9/-19) hooks/install (+5/-30) hooks/loadbalancer-relation-changed (+20/-1) hooks/loadbalancer-relation-joined (+97/-44) hooks/start (+2/-1) hooks/stop (+2/-3) hooks/upgrade-charm (+6/-0) hooks/website-relation-joined (+3/-1) inc/common (+66/-37) revision (+1/-1) |
To merge this branch: | bzr merge lp://staging/~marcoceppi/charms/precise/wordpress/apache-dog-pile |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mark Mims (community) | Needs Fixing | ||
Review via email: mp+139307@code.staging.launchpad.net |
Description of the change
This is another pretty big merge, so to you who's reviewing - first thank you! Second, sorry. Third, I'm not really.
The primary purpose of this merge is to add Apache2 as a web engine for organizations/
Other changes
- Using charm-helper-
- Removed default wp-content config value, it should have been an example, not the default
- Copyright fixes
- Added support for arbitrarily building the files from loadbalancer relation via loadbalancer-
- website relation now pushes port 8080 instead, making this charm compatible with other proxy charms if the user wants to not use the peer lb
I'm still testing support for upgrading from current version to this version via upgrade charm and any negative impacts from this. Preliminary research shows that this won't break existing installs.
multiple units are failing... tried this two ways: add-unit to existing running stack as well as deploy multiple units up front.
units come up in configure-error
I'll attach logs from one of the units.