You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dependency on ruby 2.1.0 or greater is unfortunate since 2.1 and 2.2 appear to be plagued with memory issues when running on Heroku.
For those of us still using Ruby 2.0 due to those memory issues, am I correct the gem is only used/needed in development, and only when creating migrations, and therefore it might be possible to temporarily upgrade ruby just when doing migrations but not when running the app? Eg, that there is no production behavior implemented in the gem?
I am hoping the following process might work (assuming the development machine uses rbenmv to manage both Ruby 2.0 and 2.1):
when creating and running a migration:
a) specify ruby 2.1+ in Gemfile and
b) un-comment the ar-rails gen,
c) then re-run bundle install
create and run the migration
re-edit gemfile to specify ruby 2.0 again as needed for production and comment out the ar-rails gem and run bundle install again
The text was updated successfully, but these errors were encountered:
The dependency on ruby 2.1.0 or greater is unfortunate since 2.1 and 2.2 appear to be plagued with memory issues when running on Heroku.
For those of us still using Ruby 2.0 due to those memory issues, am I correct the gem is only used/needed in development, and only when creating migrations, and therefore it might be possible to temporarily upgrade ruby just when doing migrations but not when running the app? Eg, that there is no production behavior implemented in the gem?
I am hoping the following process might work (assuming the development machine uses rbenmv to manage both Ruby 2.0 and 2.1):
a) specify ruby 2.1+ in Gemfile and
b) un-comment the ar-rails gen,
c) then re-run bundle install
The text was updated successfully, but these errors were encountered: