Ruby on Rails

On 1 July 2015 at 15:44, OPSPL Goan <lists@ruby-forum.com> wrote:
> Hi Colin,
>
> Tried that believe me. And I had the Gemfile.lock too. But it was
> erroring. Bundle install used to work - but errors after that.
>
> Now am using the bundle update (As Fred above suggested) and it's asking
> for some ruby version changes - was 1.8.5 it asked to go to 1.9.2 for
> nokogiri, then did that then now again asked to go to 1.9.3 as it's
> asking for that for capybara....

I don't think Fred suggested that, but pointed out that you may have
problems using it.
Replace Gemfile.lock with the original and run bundle install again.
If you get errors then ask for the fix. By using update you will not
end up with the same gems as on Heroku and if it does not work you
will not know whether the problem may be due to the different gem
versions or something else.

>
> So the update is still on and hopefully should work. I have no idea of
> the quality of the original code to be (able to be) upgraded across
> these versions etc. So Yes, plan to spend tomorrow reading-up on the
> tutorial you suggest. Thanks Colin.
>
> I don't want it in Git yet. I want it working on my stand-alone Ubuntu
> LTS 14.2 server here first. Then will git it.

This is absolutely the wrong approach. Put the version exactly as it
was into git first, then get it working locally. That way you will be
able to track the changes you made and easily go back when you go up a
blind alley (such as running bundle update instead of bundle install).
Such exercises are exactly where a source control system is most
useful.

By the way, the convention on this list to to insert replies into the
previous message as I have done. That way it is easier to follow the
thread.

Colin

>
> Colin Law wrote in post #1175969:
>> On 1 July 2015 at 14:32, OPSPL Goan <lists@ruby-forum.com> wrote:
>>> Hi Fred,
>>>
>>> Ok - is me, the same guy as the prev email (on this thread) Ok. Somehow
>>> it won't take my Google Login anymore - so had to create a new one.
>>>
>>> Ok trying the bundle update here. And it seems to be doing something.
>>> Will keep you informed.
>>
>> You should have copied Gemfile.lock from the working version, then used
>> bundle install
>> not bundle update. bundle install will install the versions that were
>> specified in Gemfile.lock. bundle update will update everything to
>> the latest version compatible with Gemfile, which is not the same
>> thing. Once you have it all working and in a version control system
>> such as git then you can update to later gems if you want/need to.
>>
>> If you want to find out more about RoR then I suggest working through
>> a good tutorial such as railstutorial.org, which is free to use
>> online.
>>
>> Colin
>
> --
> Posted via http://www.ruby-forum.com/.
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/7b12dd84861c6fc2343ae818eba823c9%40ruby-forum.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtvn25rVzab5xnFMVnhZpymBiYsP2sh491UyRA%3DgvwhOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.