Jeff Owens.com

We completed our subversion setup in part three, now let's add Capistrano deployment to the mix. Let's go ahead and ssh into our server:

Add the following new directories to our server. This is where our staging and production factory websites will be deployed to:

Exit out of our linux server. Run the following command to see a list of our locally installed ruby gems:

Notice we don't have Capistrano installed yet. Let's rectify that and install some other gems we'll use to add staging ability if we need it on a project:

Note that sometimes you have to try more than once to install ruby gems. If you get a timeout error just try it again. Go ahead and change directories to the new subversion project directory we had created in part three. Now we will setup our project for Capistrano deployment.

Now paste in the following deploy.rb code from this link into your deploy.rb file. Edit the line where it has set :repository and change the IP to your linux server. Save the file in nano.

Let's create a maintenance page so that if we ever need to take our site down to do server maintenance we're good to go:

Paste in the html code from this link and save the file in nano. Now let's create the folder structure for our different stages:

Let's create the mongrel_cluster.yml file for production:

Now let's setup staging:

We also need to create a config/environments/staging.rb file:

Now let's edit our database.yml file and add our stages (make sure to use your mysql user and pwd)

Paste in the following database info from the following link and save the file. Now we need to add the setup file for production:

Now we need to do the same for staging:

Now let's setup our fake domain so that we can test our deployment. Later we can replace a real domain in our staging.rb and production.rb files.

You can test it to see if our hosts file change worked by pinging our fake domains:

If you get your server's ip address we're good to go. Now let's test some Capistrano stuff out. You can see a list of the available Capistrano tasks by typing the following:

We are first interested in setting up our staging and production websites folder structure on our linux server. If we've setup things correctly so far the following commands will do that for us:

Now let's ssh back into our server and see if it worked:

You should see two folders, factory and qa.factory. Now let's install mysql (note that you will be prompted to enter a new password for root):

Next add the following line to your bash profile located in ~/.bash_profile

I like to manually create my databases and users in mysql, so let's add our databases for staging and production. You'll need to come up with a password you want to use that is secure. I'm just going to use 'password' for this example.

Exit out of the server. Now we need to change our rails project's config/database.yml, config/deploy/staging.rb, and config/deploy/production.rb files to reflect the new mysql user name of 'factory' and your new password.

Now let's add all of our rails code changes to subversion. You can see what files we need to add to subversion before we commit by typing the following:

The files with the '?' mark in front of them need to be added to subversion:

Now let's commit everything with a comment:

Now let's add our widget tunnel definition to our server and setup ssh keys for our server. Login to your server:

Exit out of the server. Now let's try deploying our staging application to the server. From the root of our factory application type the following:

You should see an error at the very bottom (/usr/sbin/monit: command not found). That's o.k. because we haven't setup monit yet. So go ahead and deploy production too:

Now add our factory tables to our staging and production databases using database migrations:

Now let's ssh back into our server and change directories to our deployed websites:

Now go to your browser on your Mac and type in http://qa.factory.com:3000. Our widget listing page should show up if everything is working. Now try creating a new widget! To stop the webrick server you just use CTRL_C. That's it for today. Next time we will get nginx to run our applications.