Merge lp:~bellini666/charms/precise/wordpress/mod_rewrite into lp:charms/wordpress

[Thiago Bellini]

It's very commom to have mod_rewrite on wordpress installations.

Also, wordpress creates .htaccess for it automatically depending on the permalink option choosen.

By enabling mod_rewrite by default on the charm, changing permalink is trivial. Otherwise, one would have to ssh to the machine just to "a2enmod rewrite".

Not to mention that, if we change the apache2 to nginx and then change back, it would need to "a2enmod rewrite" again.

[Marco Ceppi (marcoceppi)]

LGTM

review: Approve

=== modified file 'hooks/config-changed'
--- hooks/config-changed	2013-04-02 23:16:50 +0000
+++ hooks/config-changed	2014-05-13 22:40:27 +0000
@@ -76,6 +76,12 @@
 	install -o root -g root -m 0644 files/charm/apache/etc_apache2_sites-enabled_wordpress /etc/apache2/sites-available/wordpress
 	a2ensite wordpress
 
+	# Wordpress users usually use mod_rewrite. Altough it's being enabled
+	# here, it's not used by default. But, if the user changes the
+	# permalinks to something that needs mod_rewrite, wordpress will
+	# automatically create a /var/www/.htaccess to enable it
+	a2enmod rewrite
+
 	echo "apache2" > .web-engine
 else
 	if [ -f .web-engine ]; then