Where to store Application parameters

rubyonrails-talk
1

The in-memory solution would be the easiest I suppose, but if volatility is a problem then I wouldn't suggest it.

How about serializing a settings object to the database using YAML? Keep the object in memory and then drop it to the database when saved. Just use the rows to hold revisions of that object. Of course, with ActiveRecord, that's arbitrary...you could/should just create a model and do it that way probably.

The best solution is probably to use environment.rb, but since you don't want to hardcode anything, I think maybe the DB is the way to go.

--Jeremy

2

Also, if you install memcached and cached_model, then you can use your parameters as a cached object - it will stay in RAM most of the time and you'll only have slow DB calls every once in a while. Other than that it works exactly the same as normal Active Record. Jason

Jeremy McAnally wrote:

3

Checkout the Settings and AppConfig plugins at the plugin directory site. They probably have all the code you need.

http://agilewebdevelopment.com/plugins/search?search=settings