The verify hooks should deploy the boost module in the sites/all or sites/example.com directory, depending on if we're verifying the platform or the site, respectively. When verifying the site, we could also enable the module itself in the site's database so that's it's fully configured. This would allow chasing user's settings in the backend, like the Etag support.

Comments

bgm’s picture

bgm commented
Status: Active » Closed (won't fix)

Since 0.4, the boost module should first be enabled, then the site verified from aegir/provision in order to enable the rewriterules in the site vhost.

See also #976066: use boost_admin_generate_htaccess() to generate the rewriterules in the site vhost.