@ mikeytown2, Just to let you know, I have made changes to the handbook for 6.x-1.0. It better reflects the changes that went in to stable and includes a few things I missed on the last round. Yes... I still have a few things to cover and a few things to add(details and little helper things). Yep, wish it was a rewrite for next release, but that will come in time.

Your about ready for a bit of a break, maybe a little trip up through my old stomping grounds..lol I lived in Eugene Oregon for a few years before I moved to Huntington Beach CA... nope, didn't stay, came back to Ohio.. I see your doing a session at the camp.. neat. Been a long time since I ran the coast highway. Enjoy the trip, take an extra week and make a vacation out of it. The Seattle aquarium is real neat too. Maybe take a ferry up to Vancouver British Columbia, yep, you can take your car on the boat.

CommentFileSizeAuthor
#34 boost.pot35.84 KBdbeall
#33 boost.pot31.41 KBdbeall

Comments

dbeall’s picture

I reworked the handbook install page and changed the order of things.. Thinking if someone follows the steps down the page it will fall into place.
Added a section for the blocks..

a page just like it might be in order for the -dev version since it is laid out different.

mikeytown2’s picture

dev is the future, but don't go creating a whole new section for it. At least wait for point releases; 1.1 is the next release scheduled. btw test out todays dev, has some interesting new features; stole 1 idea from authcache that allowed me to do more "magic" and speed up output when page is being saved.

dbeall’s picture

will wait for 1.1 and modify existing page..
You just never stop, I will try it.

Lost a 3 month old hosting account last week(rare) and gained a new one today(strange how that works)

dbeall’s picture

Version: 6.x-1.0 » 6.x-1.01
Status: Needs review » Needs work

looks like 1.0 is history. since it was only up for a short time, rework existing handbook page should be ok.
Change status until ready for review.
Change version to current.

dbeall’s picture

Title: Boost handbook updated » Boost handbook updates

Change title, lol. It's difficult to keep up with mikeytown2.

404’s picture

Category: task » support

Two settings on handbook page that I don't understand

> # [x] Clear all cached terms pages associated with a node on insert/update/delete
> Works with view's taxonomy/term/% path as well as core.

Does this mean, when a node belongs to term/1, and it gets updated, the cached page(s) for term/1 will be cleared?

> # [ ] Turn off clean URLs for logged in users.
> Drupal will output non clean URLs for non anonymous users. This allows for the browser to cache the page and still have logging in work. This is more on the extreme side of tweaks.

Does this mean log in users will use the cached static page?

Not clear about "the browser to cache the page" ? Sounds like to instruct the browser to use browser build-in cache function.

mikeytown2’s picture

> # [x] Clear all cached terms pages associated with a node on insert/update/delete
> Works with view's taxonomy/term/% path as well as core.

Does this mean, when a node belongs to term/1, and it gets updated, the cached page(s) for term/1 will be cleared?

Yes. The cached page for term/1 will be cleared.

> # [ ] Turn off clean URLs for logged in users.
> Drupal will output non clean URLs for non anonymous users. This allows for the browser to cache the page and still have logging in work. This is more on the extreme side of tweaks.

Does this mean log in users will use the cached static page?

No, to do that; try this: http://drupal.org/node/289674#comment-2041866
What this does is allows you to remove this from your htaccess rules, and still have login's work. It's also a work around for lighttpd.
Before

  ### BOOST START ###
  <FilesMatch "(\.html\.gz|\.html|\.xml\.gz|\.xml|\.json\.gz|\.json)$">
    <IfModule mod_headers.c>
      Header set Expires "Sun, 19 Nov 1978 05:00:00 GMT"
      Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"
    </IfModule>
  </FilesMatch>
  <IfModule mod_mime.c>
    AddCharset utf-8 .html
    AddCharset utf-8 .xml
    AddCharset utf-8 .css
    AddCharset utf-8 .js
    AddCharset utf-8 .json
    AddEncoding gzip .gz
  </IfModule>

After

  ### BOOST START ###
  <IfModule mod_mime.c>
    AddCharset utf-8 .html
    AddCharset utf-8 .xml
    AddCharset utf-8 .css
    AddCharset utf-8 .js
    AddCharset utf-8 .json
    AddEncoding gzip .gz
  </IfModule>

Allows for browser side caching of your documents to work; also useful if using a reverse proxy.

dbeall’s picture

Looks like this thread kinda changed direction a bit..
The handbook page has been updated to 6.x-1.01

OFF/ON Topic?:
Should comments, #6 and #7 be added to the Tips & Tricks page?

mikeytown2’s picture

taxonomy/term info was correctly inferred; although it wasn't clear.

Go ahead and add this to the tips/tricks section
Turn off clean URLs for logged in users. - Recommend for sites that don't change much & only admin logins.

This might be of interest for that section as well
#587722: Help with using PHP to exlcude/include pages for caching

dbeall’s picture

sorry, I am trying to figure this stuff out to add to tips page, but I'm lost. I have to write it up so regular Drupal users can understand it and use it. If I can't make sense of it, many others won't either.

#289674: Supporting cached pages for authenticated users #9,#10,#11 refers to ajaxify_regions and authcache.

When harhoo reports back on #587722: Help with using PHP to exlcude/include pages for caching, then I should be able to get that in. That is, if he spells out what he did.

I added 2 notes to the settings page:

Clear all cached terms pages associated with a node on insert/update/delete
Works with view's taxonomy/term/% path as well as core.
Note: When a node belongs to term/1 and it gets updated or deleted, the cached page(s) for term/1 will be cleared.

Turn off clean URLs for logged in users.
Drupal will output non clean URLs for non anonymous users. This allows for the browser to cache the page and still have logging in work. This is more on the extreme side of tweaks.
Note: Recommended for sites that don't change much and have only administrator logins.

mikeytown2’s picture

#289674: Supporting cached pages for authenticated users disables the "is this user logged in" check. If you use Ajaxify Regions then you can sorta replicate what authcache does. This setup should be used for testing only at this time. Ajaxify Regions needs a lot of help, before I would use it on a production system.

xn2001’s picture

@dbeall
Why Transliteration and Globalredirect modules are needed?

dbeall’s picture

@xn2001
Transliteration will remove spaces and odd characters is the (URLs) or (file names) so Boost will handle them with ease, it's a utf-8 thing.(whatever that is)
Globalredirect will fix any URLs from being duplicated.. aliases vs system path; and removes the trailing slash/

I am sure mickeytown2 could write a book about it.. lol, he is a wizard.

EDIT: Boost makes my Drupal sites Rock.. even better!
Globalredirect does a lot of stuff, I guess i had in every site, even before I had Boost. Can't remember where I found out to use it...
Transliteration was for Boost, because mikeytown2 said we need it, lol

mikeytown2’s picture

Just to clarify, they are not needed, but strongly suggested. Boost doesn't have any module dependencies I know of. If there is, please let me know!

dbeall’s picture

lol, sorry, just following suggested guidelines, but we do need Drupal. I trust your knowledge and insight!
My Boosted sites are great! I said it before, you have brought Boost a long way.
I read the post by froggie about using Boost for a CDN, it just never ends. over 100KB and growing again. maybe there is room for another tab on the performance page.lol.
I think i found out about globalredirect on Drupal right after i first started, something about search engines.

dbeall’s picture

Version: 6.x-1.01 » 6.x-1.03
Category: support » task

change status back to task.. this is a task, not a support request thread.

@mikeytown2
I see this in release notes....
Note:
I recommend updating your htaccess rules from the admin/settings/performance/boost-rules page. They now change based on the settings, means you only get what you need, thus a slightly faster Boost.

Question:
Should the handbook direct people to do this instead of using boosted1.txt or boosted2.txt?
..and..
Are the boost/htaccess files going to be depreciated in the future due to this advancement?

mikeytown2’s picture

Yes, direct them to that page.

I would like to deprecate the boosted files; as it is right now, I write the php code then copy the rules into the 2 txt files. But it is useful for people who need to see it... I think thats what the default.txt file is for.

dbeall’s picture

a mental note that keeps going though my little brain...
I wish there were a way to label the htaccess tab with a shorter name.
When you write it out many times, as in instructions, it starts to hit home.
Administer > Site configuration > Performance > Boost htaccess rules generation ?

Side note: added the tip from release notes, about authcache to Tips page.

dbeall’s picture

ok, have the directions in order..The new htaccess template notes read as follows.

Additional notes for htaccess:
The module package has 3 htaccess templates included in the Boost/htaccess folder (boosted1.txt, boosted2.txt and default.txt). These templates may be helpful in some cases and are good for reference. The default.txt shows the exact placement of the rules. The boosted1.txt relying on SERVER_NAME and boosted2.txt relying on HTTP_HOST. These templates are there if you should need them. It is always best to use the htaccess generated rules from the UI as they will allow boost perform better and faster by providing custom htaccess rules tailored to your settings.

dbeall’s picture

Version: 6.x-1.03 » 6.x-1.10

added the recent changes to advanced settings section in handbook:

Clear all cached pages referenced via CCK with a node on insert/update/delete
Clear all cached views pages associated with a node on update/delete
Clear all cached views pages associated with a node on insert
Expire content in DB, do not flush file.

Just got this done, just had another look at the module page, now you have a new release out.
And I thought I had all the new stuff in there. It reminds me of the first 3 months of running D6 over a year ago.
I am a pro at upgrading. But your a PHP animal!
Boost maybe High Performance, but you still win the race...

mikeytown2’s picture

Version: 6.x-1.10 » 6.x-1.11

Having an idea where your headed is always a good idea.
#575840: 6.x Roadmap

Thanks for your hard work in keeping up with all my changes.

dbeall’s picture

I know your busy, and this is not critical --yet--
I have a question(s) that I would like to include in the handbook.
As usual, I have no idea what the answer(s) would be. I do know the subject will come up in time.

What effect does Boost have on SEO?
Do you have any SEO recommendations for Boost users?

Some SEO people recommend adding .htm to all URL aliases with pathauto.

mikeytown2’s picture

Because of faster page loading there is a slight improvement for SEO. I've had multiple reports of more page hits after installing Boost, and improved ranking on Google. In terms of improving SEO even more, assuming fast page loads = better SEO, enabling "Expire content in DB, do not flush file" would help. Just make sure cron runs consistently if doing this; or use the rules cron run trick.

Adding .html to the end of URL's is pointless, boost is fully compatible with it, but it's a dumb idea IMHO.

dbeall’s picture

updates..FYI

Added SEO to FAQ page.. thank you.

Added this paragraph under (Boost crawler) heading and the comments are being removed.

Cron starts the crawler. Each thread will grab a set number of URLs with each operation. The crawler operations will continue to run until all pages that are in the cache or have been in the cache are regenerated to the cache file. This has been done with a custom batch API. Caching new pages will be added in sometime soon.

EDIT: changed,
Caching new pages will be added in sometime soon.
Crawling new pages will be added in sometime soon.

mikeytown2’s picture

Wow, just found out about this
http://drupal.org/project/hashcash
Nice!

dbeall’s picture

It must be something good judging by your reaction...
http://www.hashcash.org/

The usage isn't very high, people just don't know about it. Which means project boost could give project hashcash a boost.
The module name is correct, but that is also why no one is using it.
If they would have named it project/spamstop, it would have big numbers.

There is no readme in the module package, there is an explanation in the .module file:
The intention of this module is to allow site administrators to add a
* hashcash hidden form field to any form for anonymous (or any defined role)
* on their site. This will prevent posting of values to the form without
* a hashcash value also being submitted. The form DOES NOT degrade when
* javascript is not available, although this may be changed so that it
* degrades to use a CAPTCHA.

mikeytown2’s picture

Version: 6.x-1.11 » 6.x-1.12

I just thought it was cool that they mention Boost in the project page. If this works with captcha comments, then that would be cool; because that hasn't been achievable in the past... boost specifically does not cache the example.com/blogpost/comment/reply part of any url. This might make it sane to cache comment pages...

dbeall’s picture

I installed it, works cool. I had to change the warning message in the .module file. I am very happy you found this, looks as it might be on my list of first installs...
it works on webform too.

dbeall’s picture

I had to stop page cache on:
comment/reply/*
hashcash/*
image_captcha/*

EDIT: i take that back.. it works on web forms with captcha, but does not seem to allow any comment submission with captcha. I will have to do some further testing someday before using it.

dbeall’s picture

Version: 6.x-1.12 » 6.x-1.13

handbook has been updated for 6.x-1.13
well, as is known at this point.

with one exception:
The rules.inc is Not included yet...
#605568: Creating a rules action to expire cached content.

mikeytown2’s picture

Found this
http://www.iskra.net/blog/ekes/2008/01/10/boost-module-and-rsynced-apach...
Would be good to add to the tricks... useful in a small server cluster.

dbeall’s picture

dbeall’s picture

StatusFileSize
new31.41 KB

roadmap looks like 6.x-1.14 will be out soon. I will keep an eye on it for doc updates.
sorry haven't been around lately for testing, node_gallery woke up and helping over there..
we might get a working beta soon(hopefully). bugs me not being a php troubleshooter on that one...
I still hunt through the code trying to make sense of it anyway..

anyway, here is a boost translation template for 6.x-1.13, it did not pick up the readme or the help folder..?

dbeall’s picture

StatusFileSize
new35.84 KB

that one is smaller.. here is the dev from today..

mikeytown2’s picture

Don't worry about giving me the boost.pot file. It's usually the last thing I add right before a new release since it depends on line numbers.

dbeall’s picture

Status: Needs work » Closed (fixed)

thread is getting too long,, close it