Bustikated

Continued from Part 1

The Godaddy Config (Step 3)

I created a database & user for the SimpleLog program, and FTP’d the program to a subfolder of my hosting root.

At this point, http://bustikated.net/mysimplelogdir/ was giving me Permission Denied errors & http://bustikated.net/mysimplelogdir/public/ was giving me Bad Request errors.

Using the phpMyAdmin db management on Godaddy’s server, I was able to modify the domain preference in the simplelog db. Trial and error later revealed that /public/ had to be present @ the end of the url, for now I just left it blank.

Also, I had to get the IP address of the server from phpMyAdmin (I couldn’t find a server name).

All of this fixed nothing

The Continuing Adventures of Step 3

database.yml

Using the Godaddy CGI Admin, I could tell that fcgi was loading, but I still wasn’t getting anything other than Bad Request errors from the site. Looking into the database.yml file, I found this support article on Godaddy’s help site.

I added port: 3306 and adapter: mysql lines.

Now I could access the front page of the blog with http://bustikated.net/mysimplelogdir/public/. But none of the links worked, and none of the stylesheets displayed.

This problem was easily solved by taking another look at Godaddy’s Rails Troubleshooting Article.

.htaccess

I added RewriteBase / to the /public/.htaccess file, and now I had stylesheets, links, and general happiness.

Log In, Please

Happiness until I tried to access the SimpleLog Admin page. If you’re not logged in, clicking the admin link (or typing in /admin in the url) redirects to the login action. This was rendering a nice message telling me to “Please Log In”, but not presenting me with any form/links to do so.

A quick, panic induced search through the SimpleLog forum revealed this. This directly contradicts the article I’d found to fix the rake simplelog:install issue I had on my personal server. Nevertheless, I ran rake rails:freeze:edge against my local install, waited for it to finish, then ran it again¹ for good measure.

Uploading the vendor/rails directory took a while, and after it uploaded ABSOLUTELY NOTHING WORKED AT ALL. Checking the CGI admin page, fastcgi wasn’t even loading. Switching back to my local install, I found that indeed the application did NOT run. So I deleted the vendor/rails directory again and my local install regained life.

Turns out that edge rake and simple log do NOT get along. Feeling quite stupid, I ran rake rails:freeze:gems, twice and uploaded the new vendor/rails folder.

And damn. Everything worked.

Step 4: Wrapping it Up

Now my blog was working. But I don’t particularly care for the busikated.net/mysimplelog/public url, so I set up a subdomain – blog, as it were – to point to the public directory. Don’t forget to update the domain setting in your db.

¹ From my experience trying to install Beast on my other computer last week.