Keep the communication lines open, let me know if you need anything in the boost module.

Comments

anarcat’s picture

Title: Let me know » Boost.module communication channel

Hi!

Thanks for dropping by! Right now, everything looks dandy. One thing that I find annoying is that I keep a copy of your boosted1/2.txt in my own repo, because it's quite hard for provision to find the boost module (something i could fix), so if you could warn me of any changes to that file, that would be really appreciate.

Great module btw ;)

mikeytown2’s picture

I don't see any global changes to the rules in the future, but I will let you know of any. BTW you know about the boost_admin_generate_htaccess() function inside the boost.admin.inc file to generate the rules based on the current settings? The boosted1/2.txt files are the lets be safe and cover everything rules, but if your not going to cache everything or if the user has set some advanced settings then the rules can change based off of the settings. Changes due to user settings is what I would be concerned about, example being I just enabled the option to control etags for files cached by boost.

ETag Settings:
(x) Do Nothing (default)
( ) Set FileETag 'None' - Do not send an etag
( ) Set FileETag 'All' - Default if enabled
( ) Set FileETag 'MTime Size' - Useful in server clusters

anarcat’s picture

The problem with provision_boost is that it doesn't necessarily have access to the boost.module. It *could*, I *think*, but right now it does not.

Furthermore, at this point, site configuration from the Aegir frontend is very limited: you don't get those settings unless you actually log into the site, at which point aegir doesn't have control anymore.

So cool! Good to know about this function, and I should use it when #616284: deploy the boost.module when verifying comes around.

mikeytown2’s picture

I'm thinking about this change. Thoughts?
http://drupal.org/node/699962#comment-2884300

bgm’s picture

Hi,

I started working on #976066: use boost_admin_generate_htaccess() to generate the rewriterules in the site vhost, but, in fact, since more recent Aegir releases, it seems that the rules from boosted1.txt cause a "bad request" response from Apache.

I detailed the error in #976066 comment #2. Do you have any hints on what could be causing this?

Thanks,
matt

P.S. regarding #699962: mod_headers directives causing high server loads and excessive bandwidth usage, I am not familiar enough with the issue unfortunately. Won't it mean that all files, including CSS and JS, will be re-downloaded after each request?

bgm’s picture

Status: Active » Closed (fixed)

Closing this issue, since there has not been much activity, and I follow the boost issue queue as well.