Pay attention to all gems that use the rdoctask
, probably they require to be updated. You can make shure in it, by entering into rails project folder, and issuing grep rdoctask * -r
.
If some of your gems use the vendor/bundle/
folder, you shall to move it to control by [tag;bundler], because since ruby-on-rails-4 the folder vendor/
is deprecated for plugins, and can be used for gems only in case, if you use non open-source or easy-to-install gems, like gems with closed property, or app-specific.
Use rvm/rbenv environments to keep gemsets up-to-date, and away of the project. Because it is useful thing to split the keep areas for various rails apps, so you will avoid encountering the similar problems that you have, to approximate to real work using heroku environment, or other servers.
If you issue bundle show rails
and get the path not leading to /usr/local
that means you used bundler version of rails that correctly load your app with bundle exec
. So, with bundle exec
you have used non-system ruby, with that you avoid the problems. I recommend to place rvm paths, before system in the path variable.
When you use rvm/rbenv don use sudo operations, if you did it already, setup proper rights to the folder:
sudo chown -R sherwyn /Users/sherwyn/.rvm
Setup the .ruby-version, and .ruby-gemset properly for each rails app you used:
echo ruby-2.0.0 > .ruby-version
echo itagora > .ruby-gemset
then reenter to the app folder:
cd ..
cd app_folder
Take a look into the answer on notice about heroku-toolbelt installation.