Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.

BlueCloth is a Ruby implementation of John Gruber's Markdown[http://daringfireball.net/projects/markdown/], a text-to-HTML conversion tool for web writers. To quote from the project page: Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML). It borrows a naming convention and several helpings of interface from {Redcloth}[http://redcloth.org/], Why the Lucky Stiff's processor for a similar text-to-HTML conversion syntax called Textile[http://www.textism.com/tools/textile/]. BlueCloth 2 is a complete rewrite using David Parsons' Discount[http://www.pell.portland.or.us/~orc/Code/discount/] library, a C implementation of Markdown. I rewrote it using the extension for speed and accuracy; the original BlueCloth was a straight port from the Perl version that I wrote in a few days for my own use just to avoid having to shell out to Markdown.pl, and it was quite buggy and slow. I apologize to all the good people that sent me patches for it that were never released. Note that the new gem is called 'bluecloth' and the old one 'BlueCloth'. If you have both installed, you can ensure you're loading the new one with the 'gem' directive: # Load the 2.0 version gem 'bluecloth', '>= 2.0.0' # Load the 1.0 version gem 'BlueCloth' require 'bluecloth'

Linguistics is a framework for building linguistic utilities for Ruby objects in any language. It includes a generic language-independant front end, a module for mapping language codes into language names, and a module which contains various English-language utilities.

PluginFactory is a mixin module that turns an including class into a factory for its derivatives, capable of searching for and loading them by name. This is useful when you have an abstract base class which defines an interface and basic functionality for a part of a larger system, and a collection of subclasses which implement the interface for different underlying functionality. An example of where this might be useful is in a program which talks to a database. To avoid coupling it to a specific database, you use a Driver class which encapsulates your program's interaction with the database behind a useful interface. Now you can create a concrete implementation of the Driver class for each kind of database you wish to talk to. If you make the base Driver class a PluginFactory, too, you can add new drivers simply by dropping them in a directory and using the Driver's `create` method to instantiate them:

This is an old, deprecated version of the Ruby PostgreSQL driver that hasn't been maintained or supported since early 2008. You should install/require 'pg' instead. If you need the 'postgres' gem for legacy code that can't be converted, you can still install it using an explicit version, like so: gem install postgres -v '0.7.9.2008.01.28' gem uninstall postgres -v '>0.7.9.2008.01.28' If you have any questions, the nice folks in the Google group can help: http://goo.gl/OjOPP / ruby-pg@googlegroups.com

This is an old, deprecated version of the 'pg' gem that hasn't been maintained or supported since early 2008. You should install/require 'pg' instead. If you need ruby-pg for legacy code that can't be converted, you can still install it using an explicit version, like so: gem install ruby-pg -v '0.7.9.2008.01.28' gem uninstall ruby-pg -v '>0.7.9.2008.01.28' If you have any questions, the nice folks in the Google group can help: http://goo.gl/OjOPP / ruby-pg@googlegroups.com

Treequel is an LDAP toolkit for Ruby. It is intended to allow quick, easy access to LDAP directories in a manner consistent with LDAP's hierarchical, free-form nature. It's inspired by and modeled after [Sequel][sequel], a kick-ass database library. For more information on how to use it, check out the [manual](manual/index_md.html).

This rubygem does not have a description or summary.

This is a collection of webservice monitoring tools for the Arborist monitoring toolkit (http://arbori.st/). It can be used to describe and monitor HTTP services in more detail than a simple port check.

Assemblage is a continuous integration toolkit. It's intended to provide you with a minimal infrastructure for distributing and performing automated tasks for one or more version control repositories. It makes as few assumptions as possible as to what those things might be. It's still just a personal project, but if you want to use it I'm happy to answer questions and entertain suggestions, especially in the form of patches/PRs. Assemblage has three primary parts: the **Assembly Server**, **Assembly Workers**, and **Repositories**. <dl> <dt>Assembly Server</dt> <dd>Aggregates and distributes events from <em>repositories</em> to <em>workers</em> via one or more "assemblies".</dd> <dt>Assembly Workers</dt> <dd>Listens for events published by the <em>assembly server</em>, checks out a <em>repository</em>, and runs an assembly script in that repository.</dd> <dt>Repository</dt> <dd>A distributed version control repository. Assemblage currently supports Mercurial and Git.</dd> </dl>

This gem adds web services to an Assemblage continuous integration server. It's still largely vaporware.

DRbService is a framework we use at LAIKA for creating authenticated SSL-encrypted DRb services that provide access to privileged operations without the need to give shell access to everyone. There are a few examples in the `examples/` directory of the gem, which are stripped-down versions of the services we actually use. The current implementation is kind of a hack, but I intend to eventually finish a DRb protocol that does the same thing in a more elegant, less-hackish way, as well as a tool that can generate a new service along with support files for one of several different runtime environments. If you're curious, see the `drb/authsslprotocol.rb` file for the protocol. This will replace the current method-hiding code in `drbservice.rb`, but existing services should be able to switch over quite easily. Or that's the intention.

An exporter for David Dollar's Foreman[https://github.com/ddollar/foreman] that outputs service directories that can be managed by 'supervise' from DJB's daemontools[http://cr.yp.to/daemontools.html].

A collection of Rake tasks and utility functions I use to maintain my Open Source projects. It's really only useful if you want to help maintain one of them.

A [Hoe](http://www.zenspider.com/projects/hoe.html) plugin for interacting with Gemnasium. It's still a work in progress.

A Hoe plugin for building interactive Rake tasks. Hoe-highline, as you might have guessed from the name, adds prompting and displaying functions from the HighLine[http://highline.rubyforge.org/] gem to your Rake environment, allowing you to ask questions, prompt for passwords, build menus, and other fun stuff.

A manual-generation plugin for Hoe. This is a plugin for Hoe[http://seattlerb.rubyforge.org/hoe/] that adds tasks and resources for generating a manual or cookbook. It's self-documenting, so for more, see {the latest manual for hoe-manualgen itself}[http://deveiate.org/code/hoe-manualgen/].

A simple, but feature-complete Ruby binding for OpenLDAP's libldap. This binding is intended as an alternative for [ruby-ldap][] for libraries or applications which require a more complete implementation of the LDAP protocol (according to [RFC4511][]) than it provides. Additions or changes: * Referrals for add, modify, delete, modrdn, compare * Controls for add, modify, delete, modrdn, compare * Asynchronous and synchronous APIs * Detailed exception class hierarchy for results instead of just one class for all non-success results. * Complete [RFC4511][] support: - extended operations and results - unsolicited notifications - continuation references - intermediate responses - alias deferencing - etc. * Cleanly abandon terminated operations where supported * Memory-handling cleanup to avoid leaks, corruption, and other problems experienced in the wild. * Drop deprecated non-_ext variants of operations which have a modern equivalent. * M17n for Ruby 1.9.x. * Improved test coverage **NOTE:** This library is still under development, and should not be considered to be feature-complete or production-ready. This project's versions follow the [Semantic Versioning Specification][semver].

A(nother) HTML(5) generator for RDoc. It uses {Twitter Bootstrap}[http://twitter.github.com/bootstrap/] for the pretty, doesn't take up valuable horizontal real estate space with indexes and stuff, and has a QuickSilver-like incremental searching.

This is a formatter for RSpec 2 that takes advantage of features in WebKit[http://webkit.org/] to make the output from RSpec in Textmate more fun. Test output looks like this: http://deveiate.org/images/tmrspec-example.png