Repository navigation
Upgrade to newer Ruby, ActiveRecord, RSpec - #294
Conversation
…of Arel until they have a release that fixes the yaml dumping bug
commented
Dec 27, 2013
|
This looks great - I'll try to make some time in the next few days to play around and make sure everything is working. Glad to be able to get back on mainline for those gems - good to see the forks have been merged and patches applied :) Could you add the new ruby to the travis build matrix in |
commented
Dec 28, 2013
|
I don't think Ruby 2.1 is suported on Openshift. Will I still be able to use stringer on Openshift if this gets merged? Thanks in advance. |
commented
Dec 31, 2013
|
I went with 2.0.0 in the Gemfile and setup 2.1.0 to run on Travis. Thanks! |
commented
Jan 1, 2014
|
@duenni i just tried deploying it on a test instance in OpenShift with the latest stringer here. The instructions in docs/OpenShift.md are still valid, except for 1 issue. The gem 'pry-byebug' depends on 'byebug' which needs Ruby 2.0 at least. So there are 2 options so far:
I tried both and the deployment to OpenShift works, with Stringer loading properly. Fetching feeds works too. Note that this is purely for production deployment to OpenShift and does not take into account the test and dev env. Not sure if this is the correct way, but if it is okay, I will update the docs/OpenShift.md docs. |
commented
Jan 2, 2014
|
I'm not even sure what |
commented
Jan 3, 2014
|
AFAIK, byebug is the replacement for debugger in 2.0 and beyond. hence the switch from pry-debugger to pry-byebug. I'll see about platform-specific declarations. |
commented
Jan 3, 2014
|
I have not used OpenShift so maybe this is a silly question but - can you configure it to just install the production environment from the Gemfile? Basically |
commented
Jan 5, 2014
|
I managed to get stringer working on OpenShift by doing the I think I will test it out on an upgrade and see if it works, then I will update the OpenShift.md docs which should conclude this issue on OpenShift hopefully. |
commented
Jan 5, 2014
|
Ran into another issue. Seems like there are some conflicts between OpenShift's activemodel and the new activemodel 4. Guess I will ask in the OpenShift forums first. |
commented
Jan 5, 2014
|
Thanks for looking into this, really appreciated! |
commented
Jan 7, 2014
|
Seems like it is a bug in OpenShift when I added the Meanwhile, the 2 methods I mentioned above still works. (Removing dev and test environment, or changing pry-byebug to pry-debugger) I just tested them. So this might be the easiest way out. I will update the OpenShift.md if there are no objections? |
commented
Jan 7, 2014
|
Yes please - go ahead and update the docs. Can always change them later if it gets resolved :) |
commented
Jan 7, 2014
|
updated :) opted for the easier way out. but wondering if it might confuse people.. maybe i should add a note indicating that it is for OpenShift production only? |
commented
Jan 8, 2014
|
@jasonngpt @swanson the issue in OpenShift is currently being addressed in this PR: openshift/origin-server#4426 |
commented
Jan 8, 2014
|
thanks @mfojtik! i didn't know OpenShift is on GitHub :) |
Ruby 2.1.0p0, ActiveRecord 4, Rspec 2.14.1, and mainline versions of feedzirra, feedbag, and sinatra-contrib.