0.04
No commit activity in last 3 years
No release in over 3 years
Create a Settings.bundle for your RubyMotion app. This allows your app to have a "global" settings entry in the Settings app.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.05
No commit activity in last 3 years
No release in over 3 years
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.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.04
No commit activity in last 3 years
No release in over 3 years
Helpers, Sass mixins, JS shortcuts, workflow and Rails settings from Evil Martians
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.1
No release in over 3 years
Low commit activity in last 3 years
There's a lot of open issues
Easy to use general purpose settings backend for activeadmin
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.05
Low commit activity in last 3 years
There's a lot of open issues
No release in over a year
Setler is a Gem that lets one easily implement the "Feature Flags" pattern, or add settings to individual models. This is a cleanroom implementation of what the 'rails-settings' gem does. It's been forked all over the place, and my favorite version of it doesn't have any tests and doesn't work with settings associated with models.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.02
No commit activity in last 3 years
No release in over 3 years
The cookie_tracker easily synchronizes settings stored in cookies with instance variables of the same name available for use in controllers and views. This gem allows you to declare a hash of parameters along with default values that you wish to be loaded/stored in the user's cookies during each page load. Each parameter will be loaded into it's own instance variable of the same name for easy access in controllers and views. If the parameter is passed in the params[] hash, the new value will automatically be stored in the correct cookie and replace the old or default value. This makes it easy to track various options that a user can select on a page, such as items per page, search queries, and custom display settings. If a user clicks off to another page on your site, their settings will be remembered when they return. You can declare the default cookie lifetime options in an initializer or override them at runtime. If you prefer to use the session store over the cookie jar, there is a method for that as well. You can override the default cookie options by creating an initializer. Visit the github page https://github.com/DanKnox/CookieTracker
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.02
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
An auto-tuning tool for internet servers w/ Genetic Algorithm and Chef. You can get good settings during sleeping ;)
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.02
Repository is archived
No release in over 3 years
Low commit activity in last 3 years
Get a nice, clean badge displaying your Rails Environment or other helpful info. Want to display last deploy date? Or maybe the status of some app wide settings? Throw it in HoneyBadger! He just doesn't care!
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.05
Repository is archived
No commit activity in last 3 years
No release in over 3 years
A lightweight singleton library for your Active Record models. 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
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.06
Repository is archived
No commit activity in last 3 years
No release in over 3 years
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
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.02
No commit activity in last 3 years
No release in over 3 years
ActiveConfiguration is an engine that exposes a generic settings store to ActiveRecord models. Made for very configurable applications, it allows you to avoid implementing specific ways to store settings for each model that needs such configuration. If your application isn't very configurable, ActiveConfiguration is probably overkill.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.02
Low commit activity in last 3 years
A long-lived project that still receives updates
Configurate is a flexible configuration system that can read settings from multiple sources at the same time.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
0.01
No commit activity in last 3 years
No release in over 3 years
Konfigurator is a small and flexible configuration toolkit, which allow you to configure your apps, classes or modules with DSL-style or Sinatra-like settings.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024