Heroku Autogenization Errors

Question

Yes, I read this one .

This is what I get in my production.log:

ActionView::TemplateError (undefined method `password' for #<User:0x2b0ddb58cdc0>) on line #11 of app/views/users/new.html.erb: 8: </p> 9: <p> 10: <%= f.label :password, "Password:" %><br /> 11: <%= f.password_field :password %> 12: </p> 13: <p> 14: <%= f.label :password_confirmation, "Password again:" %><br /> 

When I try:

 $ heroku rake db:reset RAILS_ENV=production 

I get:

 yeqynzfiku already exists (in /disk1/home/slugs/109616_e6df6f2_8837/mnt) Couldn't drop yeqynzfiku : #<ActiveRecord::StatementInvalid: PGError: ERROR: must be owner of database yeqynzfiku : DROP DATABASE IF EXISTS "yeqynzfiku"> 

I do not know what it means. I also tried

 $ heroku rake db:reset $ heroku rake db:migrate RAILS_ENV=production $ heroku rake db:migrate $ heroku rake gems:install (for what it worth) 

Everything works perfectly in place, both in development mode and in production. I have a .gems file in my application, and when I first clicked on Heroku, it seems to just install AuthLogic and Paperclip.

Dead end. Thanks.

Answer 1

It looks like you solved it, but with such problems, I think it’s convenient to do heroku restart .

For example, after starting a migration using heroku rake db:migrate application needs to be restarted before it sees these new columns.

Answer 2

Instead of db:reset try db:migrate VERSION=0 and db:migrate .
I think they have problems with reset, because it is trying to reset db.
In addition, you do not need to put RAILS_ENV=production in it by default AFAIK ...

Answer 3

I had the same problem. I did heroku restart and it worked perfectly.

Answer 4

And, something has to do with a lot of things in the .gitignore file. Had to cleanse it before putting pressure on Heroka.