Settings container, supporting nested settings

The XML registry can be used to store or retrieve app settings etc. in an XML document.

Tux dresses up sinatra in a shell. Use it to interact with your helpers, view rendering and your app's response objects. Tux also gives you commands to view your app's routes and settings.

Dependor is not a framework for Dependency Injection, but something thatt reduces duplication a little bit when doing manual dependency injection in settings like Rails apps.

sekrets is a command line tool and library used to securely manage encrypted files and settings in your rails' applications and git repositories.

A Simple Couchbase Settings gem to read RAILS_ROOT/config/couchbase.yml file

Settings gem for Ruby on Rails

iniparser - read / parse INI configuration, settings and data files into a hash (incl. named subsections)

An implementation of Array that permits chaining, where children inherit changes to parent and where parent settings can be overridden in children.

Create settings/contants for your Rails 3 app using yml key/value pairs

Add configurable settings to ruby object that can have defaults, be required, depend on one another.

An implementation of Array that permits chaining, where children inherit changes to parent and where parent settings can be overridden in children, and that retains sorted order.

Ettin handles loading environment-specific settings in an easy, simple, and maintainable manner with minimal dependencies or magic.

SimpleConfig is a plugin designed to make application-wide configuration settings (e.g. in a Rails app) easy to set and access in an object-oriented fashion.

This is the Basic Module of Rdcms. It Offers Devise, ActiveAdmin, an Article-Module, a Menu-Module, and global Settings for an CMS

A library for handling Ruby configuration settings. Inspired by the Settingslogic library but providing some additional functionality.

An implementation of Array that permits chaining, where children inherit changes to parent and where parent settings can be overridden in children, and that retains sorted order, ensuring inserted values are unique.

It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible! If you truly want that flexibility: http://github.com/stephencelis/kvc

Minimal, lightweight, multi-YAML settings

Loads from yaml, determines defaults and serves settings for the small program.