This is a test entry
If you’re reading this, know that it’s not for public consumption, it’s just a placeholder. Check back in a couple weeks when I’ll hopefully have my design finished, my old content imported, and something new and worth reading added.
I started with this excellent guide at http://mede.us/2006/12/1/mephisto-and-dreamhost. It got me most of the way there, but I found a few of the steps to be a little unfriendly to my newbie ears. I’ll try to address them here, if only to give me something to write about while I test out Mephisto authoring and work on a design.
Yada, yada, yada…
I also had a problem with ruby-dispatch failing. This kept the app from detecting changes I made to my database configuration in database.yml. Mephisto kept trying to talk to the wrong database with the wrong username and the wrong password. All it took to solve the problem was killing the ruby-dispatch process and restarting the server. I finally figured it out when Justin tipped me off to this thread at rubyonrails.org. Turned out the ruby-dispatch process just needed to be killed and the server restarted. I ham-fisted my way through a series of probably-uncomplicated-but-confusing-to-me terminal commands which, in hindsight, could have been as graceful as this:
ps axww | grep ruby
This grep will show you all the processes currently running, the names of which contain the string ‘ruby’. For each process, you’ll see a PID number and a process name. Take note of the PID for the ruby-dispatch.fcgi process and use it in the following command:
kill -9 [insert PID#]
This will stop the culprit in it’s tracks. Then you can use the standard script/server command to restart your server and hope as is fixed.
… Yaday, yada, yada…
Comments
-
This is a test comment. I just kinda wanna see how this theme styles them. Probably pretty cool.