// the take
A Ruby gem that lets any ActiveRecord model carry arbitrary settings, stored as a serialized hash in one shared table, grouped by namespace (e.g. `:dashboard`, `:calendar`) with defaults. It's for Rails apps that need per-user or per-record preferences without adding a migration for every new flag.
Adding a setting is a code change, not a migration — the serialized hash means new keys just show up with their default. The namespace model (`has_settings :dashboard, :calendar`) keeps unrelated settings from colliding on the same record. Scopes like `with_settings_for(:calendar)` and `includes(:setting_objects)` give you a sane way to query and eager-load without hand-rolling SQL against a JSON column. It's been maintained since 2012, has a real test suite with CI and coverage badges, and current releases track Rails 8.0 and Ruby 3.2+, so it's not an abandoned gem.
Settings live in a serialized hash, so you can't filter or index on an individual setting's value at the database level — anything beyond 'has this namespace' requires loading the row and inspecting it in Ruby. Validation is all-or-nothing per namespace: you subclass `SettingObject` to validate one field and that logic applies to the whole hash, there's no per-key typing or schema. The v1→v2 rewrite was a hard break with a different DSL, so if you're sitting on an old `rails-settings` install, upgrading means rewriting call sites, not bumping a version. And because every namespace is a separate row, a model with many setting groups across many records means many small rows and potential N+1s if you forget the eager-load scope.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →