OpenShift is a Platform as a Service (PaaS) from RedHat. It’s great for deploying web applications as you can setup/scale/manage apps quickly without any hassle, just like Heroku, but the OpenShift platform is available as a free and open source software, so you’re not locked in (you can install OpenShift on your server and create your own private PaaS if you want).
Previously, I’ve already written on various deployment options available for a rails application, also on deploying rails app to vps. In this article, I’ll guide you in deploying your Rails application to OpenShift.
Step 1. OpenShift Setup
First of all, Create a free Account. You get 3 small gears (resource container/unit : one small gear is equivalent to 512 MB RAM and 1GB storage) for free. If you need more, you can upgrade to premium plans.
Install rhc tool
gem install rhc
Note : If you use rbenv for managing ruby then you also need to run `rbenv rehash`.
create token and upload public keys
And follow the instructions. Once the setup is completed, you can easily create/manage your apps using this client utility (rhc).
Just type :
to see available options. If you want to see all the cartridges (application environment e.g ruby, php, python etc) available, just type :
Create a Ruby on Rails App [openshift]
Run this command from the parent directory of your project (~/parent_directory/project) or it will create a directory inside your app.
Note : joblee is the name of the Rails app we’re going to deploy. So, replace it with the name of your app. And I assume you’re using Postgresql for database.
rhc app create ruby-1.9 -a joblee
Add database cartridge
rhc cartridge add postgresql-9.2 -a joblee
Add ‘pg’ to your Gemfile. And run bundle install. Although, you’ll receive database details in the end (above command) but it’s a better to use openshift environment variables in database.yml. So, update the database.yml accordingly. Something like this one : production config for database.yml (openshift)
Step 2. Preparing the application for deployment
Once the openshift is setup, move to your project directory and setup git push deployment for your app.
rhc show-app joblee
And get the value of Git URL from the above command. Now, add the remote url for deployment. (replace GIT_REMOTE_URL with the value you got above)
git remote add openshift GIT_REMOTE_URL
Now, merge the remote repo with your development repo.
git pull openshift master
Then, you need to manually fix conflict in config.ru. Keep the default content of config.ru file.
git add .
git commit -am "fixed merge and now getting ready for deployment"
Step 3. Deploy
git push openshift master
That’s all :-). Now, your app should be live at : http://your_app_name-domain.rhcloud.com.
Note : If anything goes wrong, you can always ssh into your app server and fix things there. To ssh into your server, type :
rhc ssh joblee
ssh into the app server and type
to see lots of options available. You can also get rails console, just by typing :
bundle exec rails console RAILS_ENV=production
Postgresql Database Setup
RAILS_ENV=production rake db:setup
Assets compilation problem
I had to run few other commands on server due to some gems/assets related problems. But you can add it to openshift deployment hooks like this example rails app, so you won’t have to manually execute it every time you deploy the app.
RAILS_ENV=production bundle exec rake assets:precompile
Adding Custom Domain
First, add openshift app url (app-domain.rhcloud.com) as a cname record for www and the IP Address 188.8.131.52 (using the free redirection service) for root record. So, it will redirect root domain to www version.
Now, register that domain with rhc server.
rhc alias-add joblee www.joblee.in
If you don’t want to use www domain, then you should type this instead : (and you also need to add cname record for root domain, at your domain registrar)
rhc alias-add joblee joblee.in
Note : I’ve setup naked domain so, www version of the domain is getting redirected(301) to the root domain. Not all DNS providers supports this (I’m using namecheap and I can specify openshift app url as a CNAME record for the root record) and sometimes it can cause some weird behaviours, especially if you’re using email with the domain. (read more on how it can break MX records)