Описание модуля

Полное название: Drush
Проект начат: November 13, 2006

Описание с сайта

drush - это оболочка командной строки и Unix скриртовый интерфейс для Друпал, настоящий швейцарский армейский нож предназначенный для того, чтобы облегчить жизнь для тех из нас, кто тратит большую часть своего рабочего времени хакерствуя в командной строке.

The drush.module for Drupal 5 itself now only provides an API that allows other modules expose command line functionality in an easy way.

Also included are several modules that make use of the drush API:

drush_pm.module: The drush Package Manager: This module allows you to install modules from the command line in a very simple way (apt-get style) - just type e.g. drush pm install views in a Drupal directory to install the Views project!
Additionally, the Drush Packet Manager also allows you to update all your modules with just one command - drush pm update.

drush_tools.module: The drush Toolbox: several useful utilities for site administrators and developers (e.g. drush cron or drush cache clear)
The drush_sql module helps you issue queries to any of your databases (i.e. is multi-site aware) and even helps you migrate databases between your environments.
The drush_simpletest module is a fast and easy way to run simpletest tests from the command line.

Be sure to read the accompanying README.txt for installation and usage instructions.

More contributions both in the form of new commands for the drush_tools.module and new modules that make use of the drush API are greatly welcome!

Windows support is experimental.

"drush" - это сокращение от Drupal Shell.

Зависит от:

Update Status (5.x-2.0 или выше).

Описание модуля

Полное название: Boost
Проект начат: October 15, 2006

В Друпал 6 есть своё кеширование страниц для анонимов.

Описание с сайта

Как модуль работает

Once Boost has been installed and enabled, page requests by anonymous
visitors will be cached as static HTML pages on the server's file system.
Periodically (when the Drupal cron job runs) stale pages (i.e. files
exceeding the maximum cache lifetime setting) will be purged, allowing them
to be recreated the first time that the next anonymous visitor requests that
page again.

New rewrite rules are added to the .htaccess file supplied with Drupal,
directing the web server to try and fulfill page requests by anonymous
visitors first and foremost from the static page cache, and to only pass the
request through to Drupal if the requested page is not cacheable, hasn't yet
been cached, or the cached copy is stale.

IMPORTANT NOTES

* Drupal URL aliases get written out to disk as relative symbolic links
pointing to the file representing the internal Drupal URL path. For this
to work correctly with Apache, ensure your .htaccess file contains the
following line (as it will by default if you've installed the file shipped
with Boost):
Options +FollowSymLinks
* To check whether you got a static or dynamic version of a page, look at
the very end of the page's HTML source. You have the static version if the
last line looks like this:
<!-- Page cached by Boost at 2006-11-24 15:06:31 -->
* If your Drupal URL paths contain non-ASCII characters, you may have to
tweak your locate settings on the server in order to ensure the URL paths
get correctly translated into directory paths on the file system.
Non-ASCII URL paths have currently not been tested at all and feedback on
them would be appreciated.

LIMITATIONS
-----------
* Only anonymous visitors will be served cached versions of pages; logged-in
users will get dynamic content. This may somewhat limit the usefulness of
this module for those community sites that require user registration and
login for active participation.
* Only content of the type `text/html' will get cached at present. RSS feeds
and URL paths that have some other content type (e.g. set by a third-party
module) will be silently ignored by Boost.
* In contrast to Drupal's built-in caching, static caching will lose any
additional HTTP headers set for an HTML page by a module. This is unlikely
to be problem except for some very specific modules and rare use cases.
* Web server software other than Apache is not supported at the moment.
Adding Lighttpd support would be desirable but is not a high priority for
the author at present (see TODO.txt). (Note that while the LiteSpeed web
server has not been specifically tested by the author, it may, in fact,
work, since they claim to support .htaccess files and to have mod_rewrite
compatibility. Feedback on this would be appreciated.)
* At the moment, Windows users are S.O.L. due to the use of symlinks and
Unix-specific shell commands. The author has no personal interest in
supporting Windows but will accept well-documented, non-detrimental
patches to that effect (see http://drupal.org/node/174380).

Требования

Чистые ссылки должны быть включены и работать правильно.
Модули `path' и `pathauto' очень желательны.

In order for the static files to be correctly expired, the Drupal cron job
must be correctly setup to execute more often than, or as often as, the
cache lifetime interval you specify.

Since the static page caching is implemented with mod_rewrite directives,
Apache version 1.3 or 2.x with mod_rewrite enabled is required (if Drupal's
clean URLs work for you, you're fine; if not, get them working first).
Other web servers, such as Lighttpd, are NOT supported at present.

The `drush' module is required for (optional) command line usage.