I'm trying to figure out the best way to manage multiple sets of data
across different environments. I have a situation where I want to
automatically load some dummy data into my development environment but
I do not want that data to be loaded when I deploy to production. I
would imagine that this is a relatively common situation and I'm
wondering what people consider to be the best practice for dealing
with this type of issue.
My latest idea is to simply create data only migrations for my dev
data and just wrap the entire body of the up method with with an --if
RAILS_ENV == 'development'-- This will probably work fine for my
needs, but it seems a little hacky and the Agile Web Dev w/ Rails book
actually specifically warns against using migrations to load data not
intended for production (even though they don't follow their own
advice in the example app) so I'm thinking there's got to be a better
way or at least some existing convention for dealing with this
Any ideas or tips would be much appreciated.
Thanks in advance.