Capistrano is a utility and framework for executing commands in parallel
on multiple remote machines, via SSH. It uses a simple DSL (borrowed in
part from Rake that allows you to define _tasks_), which may be applied
to machines in certain roles. It also supports tunneling connections via
some gateway machine to allow operations to be performed behind VPN's
and firewalls.
Capistrano was originally designed to simplify and automate deployment
of web applications to distributed environments, and originally came
bundled with a set of tasks designed for deploying Rails applications.
Mocha is a library for mocking and stubbing using a syntax like that of
JMock, and SchMock. Most commonly Mocha is used in conjunction with
Test::Unit, but it can be used in other contexts.
One of its main advantages is that it allows you to mock and stub methods
on real (non-mock) classes and instances. You can for example stub
ActiveRecord instance methods like create, save, destroy and even class
methods like find to avoid hitting the database in unit tests.
Mocha provides a unified, simple and readable syntax for both traditional
mocking and for mocking with real objects.
A high-level IO library that provides validation, type conversion, and more
for command-line interfaces. HighLine also includes a complete menu system
that can crank out anything from simple list selection to complete shells
with just minutes of work.
Pioneers is an Internet playable implementation of the Settlers of Catan
board game. The aim is to remain as faithful to the board game as
possible.
It replaces the very old, unmaintained and broken gnocatan program.
With help from pioneers developer Roland Clobus
<rclobus at users dot sourceforge dot net>
ok simon@ (long ago)
- activate gtkspell support
- remove jolan@ from maintainership per his request
from new maintainer Pierre-Emmanuel Andre <pea at raveland dot org> with
some tweaks
LDAP support with group management has been added as a Trac extension.
This extension enables to use existing LDAP groups to grant permissions
rather than defining permissions for every single user on the system.
The latest release also permits to store permissions (both users and
groups permissions) in the LDAP directory itself rather than in the
SQL backend.
ok okan@
