Update defaults to what I consider "smarter" values, or even a preset selection page.
mikeytown2 - October 12, 2009 - 09:17
| Project: | Boost |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
With all these changes going in, make Boost hit the ground running. Better yet have a preset page, where one can select various presets from a drop-down.
#1
Call this the shared hosting preset. Site gets updated several times a week, updates are not time critical and only the admin has a login. This turns the cache up to the max, disregarding just about everything else. Reliable cron; no poormans; or rules cron run trick.
<?php
// Dir & File Structure
define('BOOST_NORMAL_DIR', 'normal');
define('BOOST_GZIP_DIR', 'normal');
define('BOOST_PERM_NORMAL_DIR', 'perm');
define('BOOST_PERM_GZ_DIR', 'perm');
// Caching Options
define('BOOST_CACHE_XML', TRUE);
define('BOOST_CACHE_JSON', TRUE);
define('BOOST_CACHE_HTML', TRUE);
define('BOOST_CACHE_CSS', TRUE);
define('BOOST_CACHE_JS', TRUE);
define('BOOST_PUSH_HTML', TRUE);
define('BOOST_PUSH_XML', TRUE);
define('BOOST_PUSH_JSON', TRUE);
// Advanced Settings
define('BOOST_ASYNCHRONOUS_OUTPUT', TRUE);
define('BOOST_GZIP', TRUE);
define('BOOST_AGGRESSIVE_GZIP', TRUE);
define('BOOST_CLEAR_CACHE_OFFLINE', FALSE);
define('BOOST_HALT_ON_ERRORS', FALSE));
define('BOOST_HALT_ON_MESSAGES', TRUE));
define('BOOST_CACHE_QUERY', TRUE));
define('BOOST_IGNORE_FLUSH', 1);
define('BOOST_OVERWRITE_FILE', TRUE));
define('BOOST_DISABLE_CLEAN_URL', TRUE);
define('BOOST_FLUSH_NODE_TERMS', TRUE);
define('BOOST_FLUSH_CCK_REFERENCES', TRUE));
define('BOOST_FLUSH_VIEWS', TRUE);
define('BOOST_FLUSH_VIEWS_INSERT', TRUE);
define('BOOST_EXPIRE_NO_FLUSH', TRUE);
// Crawler Settings
define('BOOST_CHECK_BEFORE_CRON_EXPIRE', TRUE);
define('BOOST_CRAWL_ON_CRON', TRUE);
define('BOOST_CRAWL_URL_ALIAS', FALSE);
define('BOOST_LOOPBACK_BYPASS', TRUE);
?>
#2
Great idea.. Food for thought to go with this..
I assume this is for personal sites? (One person login only and cron is configurable on the server)
I don't know how many other people are similar to my stuff...
My typical setup:
Cron configuration is not available on my shared host server(the one drawback).
Most of the sites I admin are small business and do qualify for this type of setting.(except 1 login)
They all use poormanscron( it's always a first install, whether the server has it or not--It's quick and easy)
They all have myself as admin
The sites (all or most all) have 1 other login, the site owner.
Although most of the site owners generally tell me to do the changes, (but not always).
The PHP rules trick is used in all of them. (great trick, I love it)
#3
Creating a "wizzard" instead of various presets might be a good idea, so it asks the user questions and guides them through the setup that matches their configuration, grouping several settings into 1.
#4
Neat idea, might be more work for you..
A wizard that creates a Todo list.
Thinking about all the non-crowd types-- might be a good thing.
I consider myself one of those types, and I have 10 Drupal 6 sites, 9 that have Boost.
The only reason I know a little more about Boost is exposure...
It is an involved module or to some--complicated.
That is why I put "this is easy" at the top of the handbook, as not to scare people away.
I suppose this is already on the config page, but a little different.
#5
Here's my todo list.
#6
this maybe out there and unnecessary..
maybe a spin off module.. project/boost_wizard
it would be a wizard that sets everything..
#7
Actually there is only 2 question that control how boost should be setup...
Do you wish to use the cron crawler?
If Yes then Enable.
* Overwrite the cached file if it already exits
* Expire content in DB, do not flush file.
* Enable the cron crawler
* Do not flush expired content on cron run, instead recrawl and overwrite it
* Preemptive Cache HTML
* Preemptive Cache XML
* Preemptive Cache AJAX/JSON
Is this an i18n site?
If Yes then Enable.
* Do not store the cache file path in the database
Disable
* Only allow ASCII characters in path
The rest should be "smart defaults" with "Turn off clean url's for logged in users" disabled even though it can give the end user a performance boost.
#8
ok, well consider this..
write up this in the readme and add some info to the handbook
#9
Going to ship with Crawler disabled & i18n disabled.
Updated Defaults.
#10
#11
Just getting going with my coffee on this end tonight..
so what do you think,
add the info from #7 to documentation about the settings..
The crawler info can be added as a paragraph in the crawler section below the explanation that I added the other day.
The i18n can be worked in as well.
#12
Adding the info into the documentation sounds like a good idea. readme.txt, handbook, both?
With these defaults, this is the new wording
Do you wish to use the cron crawler?
If Yes then Enable.
* Overwrite the cached file if it already exits
* Expire content in DB, do not flush file.
* Enable the cron crawler
Is this an i18n site?
If Yes then Enable.
* Do not store the cache file path in the database
Disable
* Only allow ASCII characters in path
The rest should be "smart defaults" with "Turn off clean url's for logged in users" disabled even though it can give the end user a performance boost. I'm leaning towards not caching xml/json by default after discovering voting api stopped working if caching XML. I have that fixed now, but how many other modules out there would be incompatible with boost out of the box?
#13
well, we never know what people are going to see or read.. some may download it, crack it open and readme.. Others don't look at the readme, they end up on the handbook or advanced help..
What i did for node gallery was put a quick run down of all the settings in the readme and added links to the handbook for more details...
why.. the readme is viewable using the advanced help module
without the advanced help, the readme has the links to the handbook.
attached is what I wrote for that one...
#14
I am adding settings tips into the Boost High Performance handbook as...
Settings Tip i18n: Enable this for an i18n site.
Settings Tip Multi-site: Enabling will allow for.....
and we still have
Notes: These are general notes about the setting.
• These are 2 different settings: xml/feed and ajax/jason ?
#15
made changes to the htaccess files
#16
Committed. Added this to the readme.txt file.
CONFIGURATION TIPS
------------------
i18n, Domain module:
Enable
[x] Do not store the cache file path in the database
[x] Flush all sites caches in this database (singe db, multisite)
Disable
[ ] Only allow ASCII characters in path
Enable XML & AJAX/JSON caches
Enable
[x] Cache .xml & /feed
[x] Cache ajax/json
Use Cron Crawler
Enable
[x] Overwrite the cached file if it already exits
[x] Expire content in DB, do not flush file.
[x] Enable the cron crawler
#17
Automatically closed -- issue fixed for 2 weeks with no activity.