Update: While it’s good to understand what you’re doing, this template file will get you so that after you get your app running,
cap deploy:setup and
cap deploy:cold works, assuming you have the host set up properly and have your app’s main directory cleared of all files.
Everybody Loves Dreamhost, but…
Dreamhost is a great little hosting company, but it really lags when it comes to keeping the latest software up to date. It’s version of Ruby is 1.8.7 and the latest stable version of Rails they have running is 3.0.3. That release is technically in “security fix” mode. Ugh.
So I’d like to run Rails 3.2, but don’t want to pay for a VPS since this system is going to be small and simple. How can I do it?
As it turns out, it’s relatively easy. I only ran into one headache and was able to install anything I wanted without any problems. How did I do this? The secret, my friends, is
Creating a new Vendored App
Let’s create a new Rails 3.2 app and set our local RVM to use 1.8.7 since that’s what passenger uses (and can’t use another version)
1 2 3 4 5 6 7 8 9
Deploying via Copy
Now you’ll need to edit your deploy file. It’s easy to deploy via copy:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
Make sure you set up your config/database.yml to include your production database connection data and let’s do a deploy
The Big Gotcha: The Asset Pipeline
Now we need to enable the asset pipeline. First uncomment the line related to it in
1 2 3 4
… and multiple platform hell.
Then we need to handle the singular headache that is related to the asset pipeline if you’re working on a different platform than Debian linux (say, OS X)
The libv8 gem that is installed and vendored on your local cache is for ‘darwin’, which is not compatible with the linux architecture. I looked to see if I could figure another way around this, but the best way I could find is to ssh in, uncomment
gem ‘therubyracer’ and run
bundle update && bundle pack on the remote box. Then I copied the
libv8-184.108.40.206-x86_64-linux.gem file in
vendor/cache down to my local vendor cache and went on my merry way.
After that, you can
cap deploy to your hearts content and you’ll have a fully deployed Rails 3.2 app on the shared Dreamhost running through passenger!