0

I'm trying to use a Rails messaging gem called "Carrier" written by a guy @stanislaw who seems to have a profile on StackOverflow

According to the ReadMe, the installation of his gem requires this command

rake carrier:install:migrations

However, when I tried it, I got rake aborted

rake aborted!
Don't know how to build task 'carrier:install:migrations'

Anyone have any experience with this gem?

Routes.rb (by request from comment below)

DeviseMessage::Application.routes.draw do


  root :to => "home#index"
devise_for :users
resources :users, :only => :show
mount Carrier::Engine => "/carrier"
Community
  • 1
  • 1
Leahcim
  • 40,649
  • 59
  • 195
  • 334
  • Hey @stanislaw, would you consider answering this question? Thanks. – Leahcim Feb 28 '12 at 02:53
  • Are you using bundler? If so did you try `bundle exec rake carrier:install:migrations`? Also could you post your `routes.rb` file? – ScottJShea Feb 28 '12 at 03:06
  • @ScottJShea bundle exec etc produced the same result. I updated the OP with routes file. Have you gotten this gem working before? – Leahcim Feb 28 '12 at 05:10
  • I have not tried it before but was going with general troubleshooting. You might have more success getting @stanislaw's input on his github page – ScottJShea Feb 28 '12 at 10:01
  • Which version of Rails are you on? I was able to get it to run with 3.2.1. – ScottJShea Feb 28 '12 at 10:21
  • I tried it with 3.1.1. The ReadMe said it was a 3.1 app. – Leahcim Feb 28 '12 at 14:31
  • @ScottJShea I installed rails 3.2.1 and was able to install migrations but then this happened. Did you have this problem? http://stackoverflow.com/questions/9494486/rails-undefined-method-paginates-per – Leahcim Feb 29 '12 at 15:54
  • Sigh, this has been a morass for you. Sadly I just encountered the same thing you did (could not remember from the last time so I just tried it fresh). I will investigate and put anything I find on your other thread. – ScottJShea Feb 29 '12 at 18:28

1 Answers1

1

I had the same error message for an engine I'm creating, and this unanswered post came top in google.

Solution for me was to run the rake task from the test/dummy directory.

As it appears you're adding this engine to your app and getting the same error, perhaps you were trying to run the rake task from within the engine directory, rather than your app directory?

See also StackOverflow question at: Rails 3.1 engines migrations are not working

Community
  • 1
  • 1
Steve Root
  • 368
  • 3
  • 13