Drush

VCS-powered blogging for Drupal.

This module is a Phoenix from the flames! New maintainer, new ideas, new challenges. Drupal 7 version on the way...

This module is abandoned in favour of:
http://drupal.org/project/drush_make_ui

Purpose

This project aims to let you create a drush make file using a UI. The primary goal is not having a UI only but rather saving all the data strucutred for later uses.

That means, that every make file is a node, every module is a part of a CCK field, which seperates the data of a module into 4 fields (server_key, short_name, api_revision, revision).

This module is designed to provide a way to export large amounts of data from views. It provides a display plugin that can rendered progressively in a batch. Style plugins are included that support exporting in the following types:

• CSV
• Microsoft XLS (or really simple HTML understood by Excel)
• Microsoft DOC
• Basic TXT
• XML

In addition proper support for Excel / the XLSX format can be added through the module Views Data Export PHPExcel.

This module is meant to provide a simple means of creating a robust command-line-driven, fully bootstrapped PHP Daemon. It uses the PHP-Daemon (https://github.com/shaneharter/PHP-Daemon) Library to create the Daemon (via the Libraries API) in order to not re-invent the wheel ;-).

#2059569: 8.x Release is in progress and 8.x-1.0-alpha3 has been released. Please test thoroughly and submit any issues you encounter.

Manage context from CLI using drush.

Please feature and related modules.

Features Scripts are command line shell scripts designed to help with building Drupal sites using Features, Drush and Drush Make. It actually automates the processes of installing new Drupal sites and adding new features to them, both used in site building.

Overview of the concept

These scripts assume the following:

This module provides more features for developers and themers when they debugging drupal.

Simple Drupal module intended to make it easy to run a queue with workers that wait indefinitely for jobs.

Such worker processes should be managed by something like Supervisord. Writing daemons should always be avoided, mkay?