I''m having a great deal of trouble getting rake to run migrations on our staging server. Everything works fine on my dev box, but trying to run the following on staging results in errors. -----> rake db:migrate(in /var/www/apps/acadtech2/app) rake aborted! Don''t know how to build task ''db:migrate'' (See full trace by running task with --trace) ---- The box has Ruby 1.8.4 and Rails 1.1.2. Any hints or suggestions appreciated. Thanks, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060725/c9ebae1e/attachment.html
I''m having a great deal of trouble getting rake to run migrations on our staging server. Everything works fine on my dev box, but trying to run the following on staging results in errors. -----> rake db:migrate(in /var/www/apps/acadtech2/app) rake aborted! Don''t know how to build task ''db:migrate'' (See full trace by running task with --trace) ---- The box has Ruby 1.8.4 and Rails 1.1.2. Any hints or suggestions appreciated. Thanks, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060725/18cf866c/attachment.html
Hello Chris,> I''m having a great deal of trouble getting rake to run migrations > on our staging server. Everything works fine on my dev box, > but trying to run the following on staging results in errors. > > ----- > > rake db:migrate > (in /var/www/apps/acadtech2/app) > rake aborted! > Don''t know how to build task ''db:migrate'' > > (See full trace by running task with --trace) > ---- > > The box has Ruby 1.8.4 and Rails 1.1.2. > > Any hints or suggestions appreciated.I haven''t the solution (are you sure you runned the command in RAILS_ROOT ?) but first, be sure you''ve got the right list of tasks by checking with : $ rake --tasks -- Jean-Fran?ois. -- ? la renverse.
Hi Jean-Fran?ois, I know for sure that I''m in the RAILS_ROOT directory, but when I run the $ rake --tasks command, I get an empty list. Any idea what could cause this? Thanks, Chris On 7/25/06, Jean-Fran?ois <jf.web3@gmail.com> wrote:> > Hello Chris, > > > I''m having a great deal of trouble getting rake to run migrations > > on our staging server. Everything works fine on my dev box, > > but trying to run the following on staging results in errors. > > > > ----- > > > rake db:migrate > > (in /var/www/apps/acadtech2/app) > > rake aborted! > > Don''t know how to build task ''db:migrate'' > > > > (See full trace by running task with --trace) > > ---- > > > > The box has Ruby 1.8.4 and Rails 1.1.2. > > > > Any hints or suggestions appreciated. > > I haven''t the solution (are you sure you runned the command > in RAILS_ROOT ?) but first, be sure you''ve got the > right list of tasks by checking with : > > $ rake --tasks > > -- Jean-Fran?ois. > > > -- > ? la renverse. > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060725/3a675266/attachment-0001.html
Solved the problem - somehow my Rakefile had gotten cleaned out. I replaced it with one from another app and it is working fine now. Thanks for the help. -Chris On 7/25/06, Chris Selmer <cselmer@gwu.edu> wrote:> > Hi Jean-Fran?ois, > > I know for sure that I''m in the RAILS_ROOT directory, but when I run the $ > rake --tasks command, I get an empty list. Any idea what could cause this? > > Thanks, > Chris > > > On 7/25/06, Jean-Fran?ois <jf.web3@gmail.com> wrote: > > > Hello Chris, > > > I''m having a great deal of trouble getting rake to run migrations > > on our staging server. Everything works fine on my dev box, > > but trying to run the following on staging results in errors. > > > > ----- > > > rake db:migrate > > (in /var/www/apps/acadtech2/app) > > rake aborted! > > Don''t know how to build task ''db:migrate'' > > > > (See full trace by running task with --trace) > > ---- > > > > The box has Ruby 1.8.4 and Rails 1.1.2. > > > > Any hints or suggestions appreciated. > > I haven''t the solution (are you sure you runned the command > in RAILS_ROOT ?) but first, be sure you''ve got the > right list of tasks by checking with : > > $ rake --tasks > > -- Jean-Fran?ois. > > > -- > ? la renverse. > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060725/f6d4ad3c/attachment.html
Solved the problem - somehow my Rakefile had gotten cleaned out. I replaced it with one from another app and it is working fine now. Thanks for the help. -Chris On 7/25/06, Chris Selmer <cselmer@gwu.edu> wrote:> > Hi Jean-Fran?ois, > > I know for sure that I''m in the RAILS_ROOT directory, but when I run the $ > rake --tasks command, I get an empty list. Any idea what could cause this? > > Thanks, > Chris > > > On 7/25/06, Jean-Fran?ois <jf.web3@gmail.com> wrote: > > > Hello Chris, > > > I''m having a great deal of trouble getting rake to run migrations > > on our staging server. Everything works fine on my dev box, > > but trying to run the following on staging results in errors. > > > > ----- > > > rake db:migrate > > (in /var/www/apps/acadtech2/app) > > rake aborted! > > Don''t know how to build task ''db:migrate'' > > > > (See full trace by running task with --trace) > > ---- > > > > The box has Ruby 1.8.4 and Rails 1.1.2. > > > > Any hints or suggestions appreciated. > > I haven''t the solution (are you sure you runned the command > in RAILS_ROOT ?) but first, be sure you''ve got the > right list of tasks by checking with : > > $ rake --tasks > > -- Jean-Fran?ois. > > > -- > ? la renverse. > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060725/60650fa3/attachment.html
Chris :> I know for sure that I''m in the RAILS_ROOT directory, > but when I run the $ rake --tasks command, I get an > empty list. Any idea what could cause this?No idea, but I would check all I can check. - Rake, - Gems Rails. Are they many versions of Rails installed ? - Rails code in vendor/rails if the application is frozen, - create a dumb Rails app, and run inside rake --tasks that''s the first suggestions I''ve got in mind. HTH, -- Jean-Fran?ois. -- ? la renverse.
Are you trying to run the migration from your app directory? I''m not sure if that will work. If that''s what you were trying to do, back up one directory to ''acadtech2'' and try again. -TJ On 7/25/06, Chris Selmer <cmselmer@gmail.com> wrote:> I''m having a great deal of trouble getting rake to run migrations on our > staging server. Everything works fine on my dev box, but trying to run the > following on staging results in errors. > > ----- > > rake db:migrate > (in /var/www/apps/acadtech2/app) > rake aborted! > Don''t know how to build task ''db:migrate'' > > (See full trace by running task with --trace) > ---- > > The box has Ruby 1.8.4 and Rails 1.1.2. > > Any hints or suggestions appreciated. > > Thanks, > Chris > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >