But if I try to spin up a new application using

$rails new_app

I get a rails app created specifically for the latest version of Rails installed.

But what if you need to create a new app for an older version of rails that is also installed? The following easy command does the trick:

$rails _1.2.3_ new_app

Where 1.2.3 is the desired version of Rails I want new_app to run. Note the underscores before and after the version.

<%= @my_array * ", " %>

The comma and space in your string will be added to the end of every string in your array except for the last one. Beautiful! I love rails.

Now for the reason for my post. While I’ve known this little trick for a while, I came across the need to titleize the outcome because my array contained all lowercase strings and I wanted to diplay them as titles.

It took a little trial and error, but the solution is rather simple:

<%= (@my_array * ", ").titleize %>

To apply the titleize method, you simply wrap your multiplication is parenthesis and add the .titleize as you normally would.

(Note: I still have not upgraded to Rails 2.0, so I cannot guarantee any of this will work in newer versions)

I’ve spent a few hours trying to get the @variables set in my controller to show up in my layout. After much frustration and trying all kinds of fancy ways around my problem, it suddenly occurred to me that I was simply loading the layout before the variables; I was loading them in the wrong order! Grrr…..

If you are having problems with variables not loading properly, check the order you call the render. It might save you a headache and the need for as much Pepsi as I went through trying to figure this stupid thing out.

In a nutshell, I used Mephisto for the conversion. First I spent about a week mapping Mephisto’s DB to WordPress’ DB. I went straight into the Mephisto Rails project and created a new model that pointed to my newly created WordPress database. I then created a controller in Mephisto that looked exactly like this:

(note: if this is a pain to read, you can also view it here)

class MephistoController < ApplicationController
    def index
        start_time = Time.now
        logger.info 'querying mephisto articles'
        @articles = Content.find(:all, :conditions=>"article_id IS NULL")
                logger.info 'querying mephisto comments'
                @comments = Content.find(
			:all, :conditions=>"article_id IS NOT NULL")
        logger.info 'querying mephisto taggings'
        @taggings = Tagging.find(:all)
        logger.info 'querying mephisto tags'
        @tags = Tag.find(:all)
        logger.info 'processing terms'
        for tag in @tags
            @wp_term = WpTerm.new
            @wp_term.term_id = tag.id
            @wp_term.name = tag.name
            @wp_term.slug = tag.name.downcase.gsub(" ","_")
            @wp_term.term_group = 0
            @wp_term.save
        end
        logger.info 'processing term relationships'
        for tagging in @taggings
            @wp_tr = WpTermRelationships.new
            @wp_tr.term_taxonomy_id = tagging.tag_id
            @wp_tr.object_id = tagging.taggable_id
            @wp_tr.save
        end
        logger.info 'processing term taxonomy'
        for tag in @tags
            c = Tagging.count(:all, :conditions=>"tag_id = #{tag.id}")
            @wp_tt = WpTermTaxonomy.new
            @wp_tt.term_taxonomy_id = tag.id
            @wp_tt.term_id = tag.id
            @wp_tt.taxonomy = "post_tag"
            @wp_tt.parent = 0
            @wp_tt.count = c
            @wp_tt.save
        end
        logger.info 'processing posts'
        for article in @articles
            c = Content.count(:all, :conditions=>"article_id = #{article.id}")
            @wp_post = WpPost.new
            @wp_post.ID = article.id
            @wp_post.post_author = 1
            @wp_post.post_date = article.published_at-7.hours
            @wp_post.post_date_gmt = article.published_at
            @wp_post.post_content = article.body
            @wp_post.post_title = article.title
            @wp_post.post_category = 39
            @wp_post.post_status = "publish"
            @wp_post.post_status = "open"
            @wp_post.ping_status = "closed"
            @wp_post.post_name = article.permalink
            @wp_post.post_modified = article.updated_at-7.hours
            @wp_post.post_modified_gmt = article.updated_at
            @wp_post.post_parent = 0
            @wp_post.guid = article.published_at.strftime("http://blog.gillumiante.com/%Y/%m/%d/")+article.permalink
            @wp_post.menu_order = 0
            @wp_post.post_type = "post"
            @wp_post.comment_count = c
            @wp_post.save
        end
        logger.info 'processing comments'
                for comment in @comments
            @wp_com = WpComment.new
            @wp_com.comment_ID = comment.id
            @wp_com.comment_post_ID = comment.article_id
            @wp_com.comment_author = comment.author
            @wp_com.comment_author_email = comment.author_email
            if comment.author_url == nil
                comment.author_url = ""
            end
            @wp_com.comment_author_url = comment.author_url
            @wp_com.comment_author_IP = comment.author_ip
            @wp_com.comment_date = comment.published_at-7.hours
            @wp_com.comment_date_gmt = comment.published_at
            @wp_com.comment_content = comment.body
            @wp_com.comment_karma = 0
            @wp_com.comment_approved = '1'
            @wp_com.comment_parent = 0
            @wp_com.user_id = 0
            @wp_com.save
                end
        logger.info 'finished!'
        end_time = Time.now
        @lapsed = end_time-start_time
        render :layout=>false
    end
end

I then proceeded to visit the /mephisto/index page on my mephisto blog, which fired this baby off. It took all of about 9 seconds to complete.

I realize the irony of using Mephisto in order to abandon it. But in the end, I wasn’t switching from the Rails based app because of Rails, but because of the app. I am still in love with rails and as you can see, this project would have taken me a lot longer to accomplish had I attempted to write it in PHP, the language of WordPress.

I’ve since realized that Typo’s development activity has gone way up, and Mephisto’s has gone way down. I have been using Typo on another blog venture of mine and am in love with it. Actually, I’m loving it much more than Mephisto these days for several reasons, most of which pertain to user friendliness. I did run into an issue with trackback spam on Typo, which I’ve read as a big complaint about it. But trackbacks aren’t even an option on Mephisto, so what’s the big deal?

The point I’m trying to make here is this. If there’s anyone out there with experience migrating from Mephisto to Typo I’d like to hear from you. There’s plenty of google hits about going from Typo to Mephisto, but nothing in the opposite direction. I’m interested in converting this blog, Tongue and Groove (once again).

$ gem_server

While it is true that WestHost now offers Ruby on Rails, it’s only available on some of the packages and not all. If you are a cheapskate like me and want to add Ruby on Rails to the Personal Starter plan where RoR isn’t available, this tutorial is for you! This even works on packages that come with RoR for those of you who are unsatisfied with how limited WestHost’s install is. I’ve adapted Aaron Gustafson’s tutorial and updated it to be more relevant, more current, and (hopefully) more helpful for 2007.

The Requisite Disclaimer: If you are on a different hosting company, I cannot guarantee this tutorial will work for you (though it may be helpful in figuring out your issues). As always, before you make changes to critical files (http.conf, .bashrc, etc.), do yourself a favor and make a backup copy; this tutorial offers assistance, but no warranty, so if you mess something up during the install, you’re on your own (but Westhost tech support should be helpful). Finally, this tutorial assumes some familiarity with the Site Manager from Westhost and some basic knowledge of the Linux shell. This tutorial uses pico as a text editor, but vi is also an option and this tutorial assumes familiarity with inline text editors. I prefer emacs, but it’s not installed by default on WestHost servers.

Now that I’ve had to muddle through it a few times, I decided that, for my own sanity and to aid anyone else out there who may be going through the same thing, I would put together a comprehensive tutorial on how to install Ruby on Rails at Westhost. The major problems that arise and could trip you up are

1. Westhost now runs Apache 2.0
2. FastCGI is not an option in some packages (and Rails will run incredibly slow without it), and
3. you cannot install applications in /usr/bin.

This tutorial will get you up and running with a very simple Rails page on your Westhost VPS server using Apache 2.0 with FastCGI. For simplicity’s sake, I am going to set up the test Rails app on its own hostname (demo.yoursitehere.com).

Required Site Applications

Before we get started, log into your Site Manager (it can be found at http://www.yoursitehere.com/manager) and make sure the following are installed:

• MySQL 5.0.27 – because you’ll want a database
• GNU Compiler Collection 1.0 – because we’ve got some compiling to do
• Perl 5.8.8 – At present I can’t remember why, but I had problems without this installed.
• FastCGI 2.4.0 (If available with your package).

Now SSH into your site and we can get started.

Step 1: Collect & unpack

First of all, make sure you are in your home directory

[yourusername][~]$ cd /home/your_username

or

[yourusername][~]$ cd ~

and then we can start the downloading and unpacking. First we get Ruby (the latest is 1.8.6 as of this writing), unpack it, and remove the archive:

[yourusername][~]$ wget http://rubyforge.org/frs/download.php/18421/ruby-1.8.6.tar.gz
[yourusername][~]$ tar -xvzf ruby-1.8.6.tar.gz
[yourusername][~]$ rm -f ruby-1.8.6.tar.gz

Next up is the latest Ruby Gem Manager (version 0.9.4 at present)

[yourusername][~]$ wget http://rubyforge.org/frs/download.php/20989/rubygems-0.9.4.tgz
[yourusername][~]$ tar -xvzf rubygems-0.9.4.tgz
[yourusername][~]$ rm -f rubygems-0.9.4.tgz

then the latest FastCGI Developer’s Kit (version 2.4.0 at present)

[yourusername][~]$ wget http://www.fastcgi.com/dist/fcgi-2.4.0.tar.gz
[yourusername][~]$ tar -xvzf fcgi-2.4.0.tar.gz
[yourusername][~]$ rm -f fcgi-2.4.0.tar.gz

and, finally, the FastCGI module for Apache (version 2.4.2 at present)

[yourusername][~]$ wget http://www.fastcgi.com/dist/mod_fastcgi-2.4.2.tar.gz
[yourusername][~]$ tar -xvzf mod_fastcgi-2.4.2.tar.gz
[yourusername][~]$ rm -f mod_fascgi-2.4.2.tar.gz

Step 2: Configure & Install Ruby

Starting in your home directory, get into the Ruby folder

[yourusername][~]$ cd ruby-1.8.6

We need to configure the source before we compile, letting it know that Ruby will be installed in /usr/local/ruby instead of /usr/local:

[yourusername][ruby-1.8.6]$ ./configure --prefix=/usr/local/ruby

Then go ahead and create the makefile and install Ruby.

[yourusername][ruby-1.8.6]$ make && make install

If you get OpenSSL errors, you can compile without (assuming you don’t want to use ssl security):

[yourusername][ruby-1.8.6]$ ./configure --prefix=/usr/local/ruby --without-openssl

[yourusername][ruby-1.8.6]$ make && make install

As we will be working with Ruby from the command line, we need it as part of our PATH, which means editing our .bashrc file:

[yourusername][ruby-1.8.6]$ pico /.bashrc

looking a few lines down from the top, you will see this line

export PATH="$PATH:/usr/local/apache/bin"

Change it to read

export PATH="$PATH:/usr/local/apache/bin:/usr/local/ruby/bin"

and save as you exit. Make sure your current session is using the new .bashrc file and then check your Ruby version (which will tell us if Ruby is working):

[yourusername][ruby-1.8.6]$ source /.bashrc
[yourusername][~]$ ruby -v
ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-linux]

Step 3: Installing Ruby Gem Manager

We will be using the Ruby Gem Manager to install pretty much every other Ruby or Rails component we need, so it is next on our list. First of all, enter its folder

[yourusername][~]$ cd rubygems-0.9.4

and then install it using Ruby

[yourusername][rubygems-0.9.4]$ ruby setup.rb

give gem a test run

[yourusername][rubygems-0.9.4]$ gem list

We don’t have any gems installed yet (other than source), but that’s what we’re doing next.

Step 4: Install Rails

Now that we have the Gem Manager installed, the rest of the basic stuff is a snap. To install Rails, simply type the following

[yourusername][rubygems-0.9.4]$ gem install rails --include-dependencies

If you get the error “Could not find rails (> 0) in any repository” you just need to run the following command:

[yourusername][rubygems-0.9.4]$ rm -f /usr/local/ruby/lib/ruby/gems/1.8/source_cache

now run

[yourusername][rubygems-0.9.4]$ gem update

and run the gem install command again.

[yourusername][rubygems-0.9.4]$ gem install rails --include-dependencies

This could take a little while, but should complete within a few minutes.

Now that we’ve done that, we can test our Rails install:

[yourusername][rubygems-0.9.4]$ cd /var/www
[yourusername][www]$ rails demo
[yourusername][www]$ cd demo
[yourusername][demo]$ ruby script/server

Open web browser to http://www.yoursitehere.com:3000/ and look what you did. Congratulations, you’ve put Ruby on Rails!

Step 5: Getting FastCGI up on Apache 2.0

(If you have a hosting package from WestHost with FastCGI, you can just install it using the manager and skip step 5 altogether. Then again, if you have that package, you can probably install Rails from there also and you aren’t in need of this tutorial in the first place.)

OK, all of that stuff was pretty easy, but know things get just a little more complex. Be warned that it gets very tedious from here on in.

First off, return to your home directory:

[yourusername][demo]$ cd ~

We need to install the FastCGI Dev Kit. To do that, enter its directory, configure and install it similarly to how we did Ruby:

[yourusername][~]$ cd fcgi-2.4.0
[yourusername][fcgi-2.4.0]$ ./configure --prefix=/usr/local/fcgi
[yourusername][fcgi-2.4.0]$ make && make install

Next on the agenda is getting Apache2 to understand FastCGI. To do this, we need to compile and install the DSO for Apache, which uses a slightly different process:

[yourusername][fcgi-2.4.0]$ cd ../mod_fastcgi-2.4.2
[yourusername][mod_fastcgi-2.4.2]$ cp Makefile.AP2 Makefile
[yourusername][mod_fastcgi-2.4.2]$ make top_dir=/usr/lib/httpd
[yourusername][mod_fastcgi-2.4.2]$ make install top_dir=/usr/lib/httpd

That put FastCGI in Apache’s modules directory, but not in the config file, so we’ll need to edit it.

[yourusername][mod_fastcgi-2.4.2]$ pico /etc/httpd/conf/httpd.conf

We need add the following in the list of already present modules

LoadModule fastcgi_module   modules/mod_fastcgi.so

Finally, create an instance of our demo app near the bottom of the httpd.conf file:

# FastCGI

FastCgiIpcDir /tmp/fcgi_ipc
FastCgiServer /var/www/demo/public/dispatch.fcgi -processes 1 -idle-timeout 60

Processes: Why only one process? Well, 1 is usually enough for most applications. If you are getting really heavy traffic, you could bump it up to 2, but FastCGI can be a bit resource hungry. It is even worse if you run multiple FastCGI servers on a single box. For instance, according to a tech at WestHost, 4 server instances running a large number of processes (say 15) each will frequently cause over 400MB of RAM and 1GB of swap to be used on the server, resulting in the cyclic behavior of freeing and reallocating memory. This is very resource intensive and it causes the server’s load to spike, which is problematic for any other users on the same server (in a VPS situation).

Step 6: Configuration

Go into Domain Management, set up a new Sub Domain Name: for your domain using the following values:

• Sub Domain Name:: demo
• Root directory for the new sub domain will be: /var/www/demo

Now configure your virtual host so that

ServerName demo.mysite.com
ServerAlias www.demo.mysite.com
DocumentRoot /var/www/demo/

becomes

ServerName demo.mysite.com
ServerAlias www.demo.mysite.com
DocumentRoot /var/www/demo/public/
ErrorLog /var/www/demo/log/server.log

Options ExecCGI FollowSymLinks
AllowOverride all
Allow from all
Order allow,deny

Save the file as you exit and then test it to make sure you didn’t screw anything up before restarting Apache:

[yourusername][mod_fastcgi-2.4.2]$ apachectl configtest
Syntax OK
[yourusername][mod_fastcgi-2.4.2]$ apachectl restart

Hang in there, we’re almost done. To set up Rails to use FastCGI, we need to edit the .htaccess file in your public folder:

[yourusername][mod_fastcgi-2.4.2]$ pico /var/www/demo/public/.htaccess

In that file, change

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

to read

RewriteRule ^(.*)$ <strong>dispatch.fcgi</strong> [QSA,L]

Then save when you exit.

Finally, we need to set up the Ruby-FastCGI Gem

[yourusername][mod_fastcgi-2.4.2]$ gem install fcgi --with-fcgi-dir=/usr/local/fcgi

Step 7: Let’s get rolling

Finally we are in a position to test our install. To do so, we’ll add a simple controller to our demo Rails install. We start by moving into the demo folder

[yourusername][mod_fastcgi-2.4.2]$ cd /var/www/demo

and then we use the Generator to make us a controller:

[yourusername][demo]$ ruby script/generate controller Say

That doesn’t do a whole lot since we have no actions. Let’s define an empty one:

[yourusername][demo]$ pico app/controllers/say_controller.rb

Edit the file to read

class SayController < ApplicationController
def hello
end
end

and save as you exit.

Now that’s all well and good, but we get an error if we try to surf to http://demo.yoursitehere.com/say/hello because there is no view associated with it. That’s easy enough to remedy, we’ll create one.

[yourusername][demo]$ pico app/views/say/hello.rhtml

Type out something simple, such as

Hello World

Hello from Rails!

The current time is

and then revisit http://demo.yoursitehere.com/say/hello. Now you’re rolling. Good luck and enjoy.

Step 8 : What? You want MySQL?

Okay, so you want to hook up Rails to your MySQL database now. To do this, there’s a few hoops you need to jump though. First of all, you’ll need to edit your database configuration file.

[yourusername][demo]$ pico config/database.yml

Fill in your database names for the development, test and production environments and the username and password for each. Then add the socket path:

development:

adapter: mysql
socket: /var/lib/mysql/mysql.sock
database: your_development_db
host: localhost
username: root
password: your_password

# Warning: The database defined as 'test' will be erased and
# re-generated from your development database when you run 'rake'.
# Do not set this db to the same as development or production.

test:

adapter: mysql
socket: /var/lib/mysql/mysql.sock
database: your_test_db
host: localhost
username: root
password: your_password

production:

adapter: mysql
socket: /var/lib/mysql/mysql.sock
database: your_production_db
host: localhost
username: root
password: your_password

and save as you exit. Without the socket information, Rails will never find MySQL, which sucks.

(This information licensed under a Creative Commons License.)

First, it’s best that the options are in an array somewhere. In this example, we’ll assume that all states are set in an array on the application.rb and the array is named $states

In the _form, or wherever your form is, do the following:

<% if @model_name and @model_name.states
@states_selected = @model_name.states.collect
end %>
<label for="model_name_states">State</label><br/>
<%= select_tag 'model_name[states][]', options_for_select($states, @states_selected), { :multiple => true, :size =>5, :id => "model_name_states" } %></p>

This will not only dynamically create your select field with each option, but it will make it so that if someone leaves off a required field the same selected states will be selected on the edit screen!

See the Rails documentation for options_for_select to customize it even further. Obviously you can leave off the :multiple and :size to make it a single select with similar results, but it’s better to use select instead of select_tag for single select combo boxes.

If you do any Ruby on Rails and want to use it with Dreamweaver, Download RubyWeaver 2.0 today!

I’ve been working on migrating this old blog to Mephisto blogging system. Mephisto runs on Rails which I have blogged about before and still continue to love and swear by.

The old blog I wrote in PHP a few years ago. I was just getting sick of re-inventing the wheel every time I wanted to add and maintain a new feature. I wanted a new system that I didn’t have to build and maintain so that I could focus more on the actual content. Mephisto also allows you to use Akismet for spam defense. Akismet is typically used with WordPress and does a great job of keeping comment spam out of your blog. I was spending way too much time removing spam from the old blog, so Akismet is a welcome change!

Also, for the sake of time, I decided to download a theme for Mephisto rather than design one myself. I chose the Lucid theme which is actually a port of the Lucid Typo theme (Typo is another Rails based blogging system). I have tweaked the default theme quite a bit to be better suited for SEO as well as handle my google ads. I also changed the default color from Ruby to Mint. But if you like the Ruby better you can change it in the upper right corner. You can also change the layout from static to liquid. These options are a few of the reasons I chose the Lucid theme.

Last but not least, I’ve finally made the transition from using Webalizer as my tracking software, to using Google Analytics instead. Google Analytics is a robust tracking application that is comparable to expensive tracking apps like Omniture but is offered as a free service. I’m extremely impressed with Google Analytics’ capabilities and how easy it is to implement. I’d recommend it for any website, big or small!

Let me know what you think of the new do.