Package Builder

Note: This project is no longer active. See Features and Ctools Exportables for config-to-code utilities.

Package Builder assists in Drupal development, site-building, and deployent by generating packages from a working Drupal installation without adding any additional dependencies. Once enabled and permissions set, users can create a package node. In the form, users can specify a name(which corresponds to the generated module name), select components and configurations, and generate a module. Users can currently select which views, content types, rules, flags, roles/permissions, users, nodes, and variable_set() configs to include. Users can also specify modules to add to the dependencies list. After clicking "Build package" Package Builder does the rest. Once completed, the package can be found in '/sites/default/files/packages/[package name]' or downloaded via a link.

From there, the generated module can be used for deployment or entirely different sites, backup, or sharing online with other site builders. Since the outputted package is just an ordered set of text files (exports), source control can be used for massive improvement in site building. In the future Package Builder will upload packages automatically to a specified repository where users can combine them with packages from other users to create new functionality.

The Ubercart project sponsored Shawn Conn's 5.x module development.
The Madhatten Project developed the 6.x module.

Note:
Exporting nodes with nodereferences doesn't keep the reference(content types with nodereferences work fine). Node uid is not preserved even if the corresponding user is exported. Downloading is also currently broken. Package Builder currently makes no attempt at tracing dependencies so be careful. This will all be fixed soon.