On 26 January 2016 at 09:52, Benyamin Pm <lists@ruby-forum.com> wrote:
> Colin Law wrote in post #1180906:
>> On 26 January 2016 at 07:48, Benyamin Pm <lists@ruby-forum.com> wrote:
>>>> not realise this shows that you really need to work through the tutorial
>>>> that I suggested.
>>>>
>>>> Colin
>>
>>> gem 'rails', '4.2.5'
>>>
>>>
>>> # Call 'byebug' anywhere in the code to stop execution and get a
>>> the background. Read more: https://github.com/rails/spring
>>> gem 'spring'
>>> end
>>
>> I don't see pg in there. As has been pointed out numerous times
>> already the error message says you need to add pg to Gemfile. Also
>> you can take out sqlite3, under the line that says
>>
>>> # Use sqlite3 as the database for Active Record
>>
>> How are you getting on with the tutorial?
>>
>> Colin
>
>
>
>
> i just edit source url from https://rubygems.org to http://rubygems.org
> and add gem 'pg' in Gemfile after like this=>
>
> source 'http://rubygems.org'
>
>
> # Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
> gem 'rails', '4.2.5'
> gem 'pg'
>
>
> and i go to terminal and type 'gem install pg'
You should have run
bundle install
or just
bundle
there is no need to run gem install pg though it will not do any harm.
> then type=> bunlde show pg
> and i get the path=> /var/lib/gems/2.1.0/gems/pg-0.18.4
>
> befor that , when i type this. i get this=> Could not find gem 'pg'.
>
>
> now the error is Gone! ;)
I am surprised the error is gone if you have not run bundle install or bundle.
Colin
--
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%3D0gLupRb-mbdjfWH3_pvaLC4_LYdTbtbTuAu3bTAMa4F5uJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment