SOLVED
I figured it out. I found on a blog [
http://www.jsiegel.com/2008/10/heroku-databaseyml-and-no-such-file-to.html]
that this was due to having Rails frozen in vendor/rails. I deleted the
frozen Rails, and it worked. I never read anything on Heroku about not
supporting vendor'd Rails. Oh well
I've tried just about every configuration in database.yml that I could think
of. I changed the adapter to postgresql and then got this error when
deploying via git:
Running migrations...
rake aborted!
could not connect to server: No such file or directory
Is the server running locally and acceptin
On Sat, 22 Nov 2008, Keenan Brock wrote:
> That is a little strange as I thought Heroku was running postgress
That would explain why it couldn't connect to the local MySQL socket. :)
> On Nov 22, 2008, at 4:05 AM, Nate Clark <[EMAIL PROTECTED]> wrote:
>> I must be missing something here ... I'v
That is a little strange as I thought Heroku was running postgress
Maybe you checked in the database config? Or a separate plugin expects
it? Or you are directly calling connect on active record base?
On Nov 22, 2008, at 4:05 AM, Nate Clark <[EMAIL PROTECTED]> wrote:
>
> I must be missing
I must be missing something here ... I've imported my app, deploying
it via git, and when Heroku tries to run the migrations I get:
Running migrations...
rake aborted!
Can't connect to local MySQL server through socket '/var/run/mysqld/
mysqld.sock' (2)
I was under the impression that the databa