Connecting to MySql on Dreamhost

[rgremill]

Is anyone here using Dreamhost to develop Rails?

I can't even get passed step one.

How do I configure the database.yml file so that I don't get the following error?

Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Thanks in Advance!!

[xmitchx]

I use dreamhost and I connect just fine. What host (for the database) are you using? You're not using 'localhost' are you?

[rgremill]

Do you have an example database.yml file so I can see what you do?

[vgarcia]

See if this helps you: http://wiki.rubyonrails.com/rails/pages/database.yml

[rgremill]

Thanks for the link.

I wish I could just get the output of an actual Dreamhost database.yml that works.

I guess I'll contact support today.

Thanks!

[xmitchx]

here is an example database.yml:

 development:
   adapter: mysql
   host: my-db.mitchellhashimoto.com
   user: mitchell
   pass: ***...
   database: my_db

just like that...

[samsm]

Remember the host! Localhost is the default for most database setups but that is always wrong on Dreamhost.

Have you set up a database yet? That is also a necessary step.

[xmitchx]

Right.

Also, remember that on Dreamhost it takes about a day for your DB host to start working because the subdomain has to propagate. And also, if you are waiting for it to propagate and wish to find the exact IP of it, just open up a SSH client and log in. Then do a:

 wget http://my-db-host.my-domain.com

And you can find out the IP (even though the wget wont work ) then just use the IP as the host.

[samsm]

Also, remember that on Dreamhost it takes about a day for your DB host to start working because the subdomain has to propagate.

It isn't instant, but it takes less than a day. 10 minutes is the mode I've experienced.

Once you can get to phpMyAdmin through the control panel, the domain works.

[xmitchx]

It isn't instant, but it takes less than a day. 10 minutes is the mode I've experienced.

Once you can get to phpMyAdmin through the control panel, the domain works.

Ah, I have roadrunner and domains are slow to propagate, takes about a day for me.

[rgremill]

My database.yml file didn't have the host line in it when it was generated.

It appears to have worked after adding it.

I ran the scaffold command and didn't get any errors. I can see that the pieces have been created.

Thanks for all of the help!

Now I have a new problem. I can't get to the scaffold. Is there something special I need to do with the dreamhost domain settings? or htaccess files?

I was expecting it to show up here: http://www.boardrunners.com/post/admin

[vgarcia]

Are you running FastCGI on your domain? If so, be sure your .htaccess file forwards requests to dispatch.fcgi instead of dispatch.cgi (or vice-versa if you're running your Rails app as CGI, which is really slow and not recommended).

[rgremill]

Do you have an example htaccess file also?

Getting started is always the toughest part, huh? :-)

[vgarcia]

If you have a line that looks like this:

RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

You'll have to add an "f" after the last dot if you're using FastCGI.

[samsm]

I was expecting it to show up here: http://www.boardrunners.com/post/admin

ruby script/generate scaffold whatever

The scaffold should be accessible at:
http://example.com/whatever

I think CGI and FCGI are active on Dreamhost (when you check the box for FCGI to be available) so I expect your .htaccess is fine either way.

[rgremill]

Thanks for the help. I found this link http://wiki.dreamhost.com/index.php/Ruby_on_Rails

I'll be studying it tonight!!

I may be looking for a Rails tutor if anyone is interested!

[xmitchx]

If you have a line that looks like this:

RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

You'll have to add an "f" after the last dot if you're using FastCGI.

But wouldnt doing this cause changed source files to not reload?

[samsm]

But wouldnt doing this cause changed source files to not reload?

Glad you asked.

When you change files in the app directory, go ahead and kill all the active fcgi dispatch processes. The new processes that apache spawns will reflect your changes.

Really, you should be testing stuff in your localhost environment and then uploading it once you are sure it works, minimizing the above step.