
Well, this is not something I expected. I suppose a lot of people would figure it out quickly enough, but it's really something they should say outright.
In my previous post, I basically said, Heroku told me to change rails versions, so I did, and then went on about fixing all of the things that broke in my code. Then, I talked with someone who said "just freeze the rails version." That sounded like a fantastic solution, the rails version would run local to my application, and it wouldn't matter what versions of rails Heroku had installed. Fantastic news. This won't break any gems not supported by earlier versions of rails (2.1 and... ). Except, it doesn't work.
This post covers the topic well. His point that the error is cryptic is well taken, but it's worse than that. We're talking about errors, not error. So his suggestion of Heroku issuing a "Don't Freeze Rails!!!" warning is especially prudent considering that his error and the one I got are not the same.
His:
MissingSourceFile in DashboardsController#index
no such file to load -- sqlite3
RAILS_ROOT: /mnt/home/userapps/xxx
Mine:
Mysql::Error in MyController#index
Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
RAILS_ROOT: /mnt/home/userapps/47584
I don't know why the errors are different. Different frozen versions? Either way, I guess it's back to figuring out how to retrofit my app...
No comments:
Post a Comment