Once you have a Ruby on Rails production sever set up, its time to look at deployment options. The most well known has got to be Capistrano, which allows you to deploy changes by running simple commands. It can be confusing to set up, so here’s a guide taking you through the deployment process.
You are going to need a Rails production sever and a git repository of your project, in order to deploy with Capistrano. Additionally you will want a special Deploy user with limited permissions for Capistrano to use. I wrote a few guides to take you through everything.
As for the Git repository, you can simply use GitHub, or if you want I wrote a tutorial Installing git from source.
Now let’s take a look at what we’ll be doing throughout this guide.
- We’ll install Capistrano locally in our app.
- We’ll configure Capistrano for our server and repository.
- We’ll deploy our application using Capistrano.
- We’ll create a database and fix any problems we run into.
Installing Capistrano on our app
This parts super easy, it’s just a couple gems! Start by navigating to the root on your Ruby on Rails application locally. Open the Gemfile, and add the Capistrano gems.
Save, exit, and run the following commands in Terminal.
bundle install cap install STAGES=production
This will install the Capistrano Gems and create all the Capistrano configurations files within our app. Easy enough, right?
From the root of your application, open the Capfile. We need to add a couple lines, make yours look like the example below.
Now open config/deploy.rb, replace the contents with the code below, be sure to change the application name, repository url, and deploy root.
Last but not least open config/deploy/production.rb and edit it to look like the example below. Be sure to replace the sever IP with your own.
That’s about it, we’re all configured and ready to give deployment with Capistrano a try.
Deploying with Capistrano
Now that we’re all configured and ready to go, cross your fingers and run the following command to test the configuration and connection.
cap production deploy:check
Error: Finished in 0.055 seconds with exit status 1 (failed). ERRORlinked file /var/www/yoursite.com/shared/config/database.yml does not exist on 543.543.345.543 cap aborted!
Oh no, what happened here? It looks like we forgot to create the database.yml and secrets.yml files that we linked while editing deploy.rb. Lets do that now.
ssh email@example.com cd /var/www/yoursite.com/shared/config nano database.yml
Paste your database.yml file here. You can edit out all the development bits. Be sure to set the user and password for your sever MySQL account
Save and exit. Now let’s create one for our secrets.yml file.
Paste the following code, replacing with your own secret key base
Note: If you don’t have a secret key base already, you can generate one by navigating to the root of your application locally and running rake secret
Alright now that the files are in place, let’s try this again.
cap production deploy:check
Success: cap production deploy:check Finished in 0.048 seconds with exit status 0 (successful).
Awesome looks like everything is configured correctly and working. Now let’s deploy our application for real. Run the following command.
cap production deploy
Success: Finished in 0.057 seconds with exit status 0 (successful).
It looks like we’ve deployed successfully, but when we open our website in the browser, we see an error message. After checking our production log at
/var/www/yoursite.com/current/log/production.log we discover that we haven’t created/migrated a database yet. Do this by running the following commands.
ssh firstname.lastname@example.org sudo -i # Gain root cd /var/www/yoursite.com/current bundle exec rake db:create RAILS_ENV=production bundle exec rake db:migrate RAILS_ENV=production service nginx restart
Refresh your website in your web browser and you should be in business! Any problems, questions, or feedback just leave a comment below.