Colin Law wrote in post #1175974: > On 1 July 2015 at 15:44, OPSPL Goan <li...@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
Ok Got that. thanx. For the convention part. Will do. Now about the coding thing - Ok am up a blind alley now. It upgraded everything - but still won't run. no bundle errors... But well :-( It asked for a config.rb file and such stuff :-( Said puma was not available, etc etc... and then says this..... 20:56:07 wweb.1 | started with pid 3438 20:56:07 worker.1 | started with pid 3440 20:56:08 worker.1 | /home/online/.rvm/gems/ruby-1.9.3-p551/gems/rake-0.8.7/lib/rake/alt_system.rb:32: Use RbConfig instead of obsolete and deprecated Config. 20:56:08 wweb.1 | /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/dsl.rb:20:in `read': No such file or directory - config/puma.rb (Errno::ENOENT) 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/dsl.rb:20:in `_load_from' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/dsl.rb:9:in `block in load' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/dsl.rb:8:in `tap' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/dsl.rb:8:in `load' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/configuration.rb:35:in `load' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/cli.rb:545:in `parse_options' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/lib/puma/cli.rb:190:in `run' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/gems/puma-2.11.3/bin/puma:10:in `<top (required)>' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/bin/puma:23:in `load' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/bin/puma:23:in `<main>' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `eval' 20:56:08 wweb.1 | from /home/online/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `<main>' Any thoughts. But tomorrow (is 9 PM here now so leaving for the day) - I will do as you suggest - try getting down a clean copy, put it into git and then try and slowly upgrade/build it. Thanx for the attention. Goan. -- 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+unsubscr...@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/6aa66e6d22cc55b78dd37c7d0e94bfef%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
