Language selection

  • English


    Release Cycle / Updates

    Release Cycle The Drupal WxT 7.x-4.x branch will be updated with a stable release approximately once every few months roughly around the 18th. The reason for this is to follow as closely the Drupal security and core release cycle which is usually around the 15th of every month. 1.x branch Starting in January 2016 there will be no more new features integrated into the 7.x-1.x branch. Only security and minor bug fixes will be merged into the codebase for a period of 6 months.


    Vision Statement The Drupal WxT distribution is a web content management system which assists in building and maintaining innovative Web sites that are accessible, usable, and interoperable. The primary goal of Drupal WxT is to provide an enterprise level platform that can assist governments and larger organizations in disseminating data. Mandatory Features There are a lot of features inherently provided by Drupal WxT. However there are a few that have been designated as mandatory to support and as such have shaped the architecture of the distribution.

    Apache and PHP-FPM

    Important Want even more performance? Head on over to our Nginx + PHP-FPM documentation. Apache can achieve a rough parity in performance to a Nginx + PHP-FPM setup. With the added caveat that Apache should be run in either MPM Event or MPM Worker mode. Please note that the following statement holds true when analyzing performance: page speed < requests served This means we are more concerned about how many requests that can be served then how fast we can serve the request.

    Nginx and PHP-FPM

    Important Using Apache? Head on over to our Apache + PHP-FPM documentation. Nginx is event-based, so it does not follow Apache’s style of spawning new processes or threads for each web page request. The end result is that even as load increases, memory and CPU usage remain manageable. Scenario Server with the following technical specs: CPU: 4 @ 2.7GHZ RAM: 8GB Quick Audit Nginx There are three key areas to inspect when looking at Nginx for a PHP-FPM environment.

    Libraries API

    Libraries API is the common denominator and the defacto standard for all Drupal modules/profiles/themes that integrate with external libraries. The module introduces a common repository for libraries in profiles/distro/libraries or sites/all/libraries. Key Features The same library can be shared by more than one module. The same library can be shared by more than one site. Ease the process of upgrading a module that requires an external library. Just replace the module folder with the new one.

    Profiling with XHProf + XHGui

    XHProf is a function-level hierarchical profiler for PHP. The raw data collection component is implemented in C (as a PHP extension). It is capable of reporting function-level inclusive and exclusive wall times, memory usage, CPU times and number of calls for each function. Additionally, it supports ability to compare two runs (hierarchical DIFF reports), or aggregate results from multiple runs. XHGui is a tool built upon XHProf to facilitate both an improved user experience and a more efficient storage of metrics via optional support for MongoDB.

    Content Staging with Deploy + UUID

    Deployment with Drupal WxT There are 4 essential modules that facilitate deployment in Drupal WxT: WetKit Deployment: Provides the base configuration for both source and destination servers as well as default content types WetKit Deployment Environment Indicator: Provides contextual environment information (.dev, .qa, .prod) on the toolbar WetKit Deployment Source: Provides the functionality to deploy content in JSON to the destination servers WetKit Deployment Destination: Provides the CRUD interface to consume the JSON data that was sent from the client server

    Drush Make + Site Install

    Important These instructions could become outdated over time. Up to date instructions can always be found via the official readme. Drupal WxT uses Drush Make for a rapid built-out of the Drupal codebase. A drush make file is similar to an “ant script” and allows us to host just the code that we are developing (Installation Profile and Custom Modules, Features, and Themes) on GitHub. Any user who has Drush installed can then perform a build-out of both the Drupal Core package and various contributed modules hosted on Drupal.

    Getting Started (Windows)

    Important The most up to date instructions are available in the file. This page while outdated does contain additional procedures for custom environments. Install Acquia Dev Desktop If this is your first Drupal 7 install, you may want to install the Acquia Dev Destop on your machine since it will provide you with a complete environment at the click of a button. It will set up Apache, MySQL, PHP and install an instance of Drupal.

    System Requirements

    Drupal WxT can run on a wide range of desktop and server operating systems including Windows, MacOS, Linux and UNIX. However, you will need to configure the environment according to the standard Drupal 7 requirements. This page provides a brief summary of those requirements and recommendations. More information is available from the system requirements page at Web server Apache 2.x Microsoft IIS NGINX Database server PostgreSQL 8.