Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is it only needed when creating/running migrations (proposed ruby version issue workaround) #1

Closed
jpwynn opened this issue Jun 14, 2016 · 0 comments

Comments

@jpwynn
Copy link

jpwynn commented Jun 14, 2016

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):

  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
  2. create and run the migration
  3. 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
@fnando fnando closed this as completed in c946d65 Jun 24, 2017
fnando added a commit that referenced this issue Jun 24, 2017
This doesn't mean that all versions are supported; latest version is recommended at all times.
fnando added a commit that referenced this issue Jun 24, 2017
This doesn't mean that all versions are supported; latest version is recommended at all times.
fnando added a commit that referenced this issue Jun 24, 2017
This doesn't mean that all versions are supported; latest version is recommended at all times.
fnando added a commit that referenced this issue Jun 24, 2017
This doesn't mean that all versions are supported; latest version is recommended at all times.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant