Drush
dgo.to
Component type
Maintenance status
Development status
Component created
Component changed
Overview
This is a Drush extension that pings http://dgo.to to retrieve user ids from user names or IRC nicks.
Project Status
Component type
Categories
Maintenance status
Development status
Downloads
Component created
Component changed
Project status is an extension for drush which takes a list of Drupal platforms as arguments and returns a list of modules which are in use or not in use by the sites within these platforms. It is able to list all modules, or only those which are in use, by platform and site. By default it only reports on modules within sites/all/ or sites/default/, but it can optionally report on modules within site directories as well. Results are grouped by project (for example, the modules views and views_ui are shown together as views) unless an option is given to list each module separately.
In brief, this module was written to answer the question, "which modules in this shared platform are actually in use, and by which sites?"
Octopus
Component type
Categories
Maintenance status
Development status
Downloads
Component created
Component changed
The Octopus (part of BOA) project has moved to Github!
* Use our Github project for contributing code, or reporting bugs, or requesting features.
* There is also a Gitter community channel.
New releases announcements are posted on Twitter
WALID
Component type
Categories
Maintenance status
Development status
Component created
Component changed
One Appliance to Rule Them All
Well, to make them play nice together anyway...
I was looking for a production/staging server build script or appliance that had LAMP, Webmin, Aegir, ISPConfig, and all the Drupal dependencies on top of a long term support (LTS) version of uBuntu.
On top of web and database services, I also wanted email and DNS, open source anti-spam and anti-virus, a firewall, and protection from DOS and other similar attacks. I also wanted all my admin interfaces to use SSL and I wanted secure SMTP enabled.
Basically, I wanted the offspring of a debaucherous affair between Webmin, Aegir, a slightly hardened LAMP, ISPConfig, and Drupal. I wanted - WALID.
Meet WALID. It's that genetically engineered super offspring.
WALID's the output of a build script that smaller-scale Drupal developers can use to quickly build a production server on a Cloud or Dedicated VPS (or download as an appliance). For Drupal developers that need more than shared hosting but aren't experienced in building or maintaining Linux servers, this will get you going. For developers who have reached a certain level in their Drupal-fu but who aren't experienced with Linux, WALID is a relatively secure and stable Drupal-centric production environment that can be managed via secure web interfaces by even non-Linux pros. [This is the goal anyway...]
Drush Body Mangler
Component type
Maintenance status
Development status
Component created
Component changed
This is not a module, but a drush script, which is a fairly straight-forward exercise in string manipulation, searching for links (anchor tags) that are missing title attributes. It does this in a very crude way, searching only the body field as rendered by a node_load() call.
However, the exercise of writing it (and the preceding hunt for some Drupal Best Practice on this) was instructive. One can imagine any number of uses for a script(s) like this, if it had some features like:
Drush Environments
Component type
Categories
Maintenance status
Development status
Component created
Component changed
This is a very basic drush plugging.
What this does is allow you to set up "Environments" options in your drushrc.php file so you can easily do a set of task you when enable a certain environment.
One example of this is enabling views_ui, devel, and turning off js preprocessing when you're developing
Instead of having to run the same set of drush commands every time you bring in a new database from production you can just now set up your environments and just call drush en-env development and viola ;-)
Drush site re-upgrade script
Component type
Maintenance status
Development status
Component created
Component changed
[not a module] This is a script to run the database upgrade of a Drupal site from 6 to 7 while re-using an established codebase.
Update: This script is deprecated in favor of a two-command process:
Features Export Language
Component type
Component created
Component changed
This module switches language to Drupal's basic default language, which is exclusively English, when exporting, recreating or updating a Feature.
Usually if a features is getting exported, the language of the site is used. That means that in special cases (f.e. views names) you get a translated string.
jmac
Component type
Categories
Maintenance status
Development status
Component created
Component changed
this is a test site - jmac
