Settings container, supporting nested settings

Use this as a quick start to get rubocop with the settings we use at bitcrowd into your project

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.

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

Chamber lets you source your Settings from an arbitrary number of YAML files and provides a simple mechanism for overriding settings from the ENV, which is friendly to how Heroku addons work.

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

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.

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

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

Settings gem for Ruby on Rails

Minimal, lightweight, multi-YAML settings

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.

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.

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

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

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.

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

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