Commander

In simpler terms Commander allows developers to add support for the Ruby terminal.

This means developers or even end-users will be able to open the Ruby console, type a few commands and change settings or the behavior of their Ruby website or service.

While developers find this very attractive, the notion of running a combination of operations in a row and save some time, Commander must be used with care when end-users are involved.

This is because an in-experienced user can very easily crash an application if he does not know what he's doing, or the CLI has not been thoroughly tested in advance.

Commander has also been the base for Commander.js, a similar tool for Node.js.

What is new in this release:

• Fix various Ruby warnings for circular requires, etc.
• Update to use highline 1.7

What is new in version 4.3.0:

• Prevent deprecation warning when loaded in a Rails 4 environment.

What is new in version 4.1.0:

• Make optional arguments true when present.

What is new in version 4.0.7:

• Improved support for JRuby and Windows (and any other platforms that don't support Kernel.fork).
• Fixed bug #33 - support `-help` after commands.
• Reorganized help output to display synopsis before description.

What is new in version 4.0.6:

• Improved load time on Ruby 1.9.
• Updated documentation.

What is new in version 4.0.5:

• Improved rake tasks for gem development.
• Added say_ok, say_warning and say_error methods to print messages in green, yellow or red.
• Fixed; Allow global options to be passed in any order, even mixed with command options.
• Fixed; Global options can be passed before or after the command, they can even be mixed with command options.
• Fixed; Platform test should now correctly identify JRuby.
• Fixed; Add to_s to exceptions as option parser no longer does implicit conversion.