active_record_migrations
active_record_migrations copied to clipboard
Enable pessimistic gemspec
We have a project that needs migrations and is also included in a Rails app. Due to the locked 4.0.1 gemspec this reverts our Rails version to 4.0.13. Looking at the Rails Active Record Migrations code base, I think this is the only piece missing to make this work back to 2011 code base?
Hi Michael, could you please check out the optimistic branch I just created?
https://github.com/rosenfeld/active_record_migrations/tree/optimistic
Anyway, I'm curious, why are you using active_record_migrations if you already have a Rails app which contains the AR framework?
I have an engine that is used with a rails app but is also used in another standalone app as pure gem. So then I have both situations occurring with one shared dependency. I'll check out the branch on Tuesday, thanks for taking a look.
Sorry -- I didn't state that very clear. We have a gem that uses active record and migrations which is included in various projects. Some of which are Rails Engines/Apps others are stand alone 'services' users RabbitMQ etc to communicate out.
Closing due to inactivity.