Thanks, Keenan. That fixed it. Heroku recommended updating all Legacy models, like so:
if Rails.env.development? class LegacyModel end end That works too, but your solution is nicer because you don't have to tweak every model. On Dec 3, 10:01 am, Keenan Brock <[email protected]> wrote: > Why not try app/models_legacy/ > That is not included by default in rails. so you could get a difference. > > Best of luck, > Keenan > On Dec 3, 2009, at 11:26 AM, Patrick Crowley wrote: > > > > > My app won't launch because it has some Legacy models that rely on > > a :legacy database adapter. > > > I have no intention to use these models in production -- they're only > > used to migrate legacy content. So my plan is to just run my legacy > > migration rake task in development, migrate all legacy data, and then > > push the data to my Heroku app. > > > Sure, the easy fix would be to just ditch the models entirely, but > > realistically I'll need to migrate legacy data repeatedly until the > > app is completed and launched publicly. > > > So how can I tell Heroku to ignore these models? > > > I've tried this: > > config.load_paths += %W( #{RAILS_ROOT}/app/models/legacy ) unless > > RAILS_ENV == 'production' > > > But Heroku seems to ignore it. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
