Gem Version
gem install fog

Having Ruby experience makes you hirable; but how can you stand out? You need to demonstrate your abilities. What better way than using Ruby and “the cloud” to store and serve your resume!

In this blog post you will learn to use fog - the cloud computing library - to upload your resume to Amazon’s Simple Storage Service (S3), Rackspace’s CloudFiles or Google’s Cloud Storage.

Here’s my out of date resume stored on S3, CloudFiles and Google Storage; programmatically stored in the cloud using this tutorial. NOTE: my boss would like me to add that I’m not currently looking for a new gig ;)

Check out those cloud-specific URLs! You could put all three in your job application, add the Ruby source for how you did it, and have your choice of Ruby jobs for being so awesome!

How? The all-clouds-in-one library of choice is fog.

Installing fog

fog is distributed as a RubyGem:

gem install fog

Or add it in your application’s Gemfile:

gem "fog"

Using Amazon S3 and fog

Sign up for an account here and copy down your secret access key and access key id from here. We are about to get into the code samples, so be sure to fill in anything in ALL_CAPS with your own values!

First, create a connection with your new account:

require 'rubygems'
require 'fog'

# create a connection
connection ={
  :provider                 => 'AWS',
  :aws_access_key_id        => YOUR_AWS_ACCESS_KEY_ID,
  :aws_secret_access_key    => YOUR_AWS_SECRET_ACCESS_KEY

# First, a place to contain the glorious details
directory = connection.directories.create(
  :key    => "fog-demo-#{}", # globally unique name
  :public => true

# list directories
p connection.directories

# upload that resume
file = directory.files.create(
  :key    => 'resume.html',
  :body   =>"/path/to/my/resume.html"),
  :public => true

If you are anything like me, you will continually tweak your resume. Pushing updates is easy:

file.body ="/path/to/my/resume.html")

As you can see, cloud storage files in fog are a lot like an ActiveRecord model. Attributes that can be changed and a #save method that creates or updates the stored file in the cloud.

But if it took you longer to realize the mistake you might not still have file around, but you’ve got options.

directory = connection.directories.get("proclamations1234567890")

# get the resume file
file = directory.files.get('resume.html')
file.body ="/path/to/my/resume.html")

# also, create(attributes) is just new(attributes).save, so you can also do:
file ={
  :key    => 'resume.html',
  :body   => 'improvements',
  :public => true

Backing up your files

Now you’ve got a bunch of files in S3: your resume, some code samples, and maybe some pictures of your cat doing funny stuff. Since this is all of vital importance, you need to back it up.

# copy each file to local disk
directory.files.each do |s3_file|, 'w') do |local_file|

One caveat: it’s way more efficient to do this:

# do two things per file
directory.files.each do |file|

than it is to do this:

# do two things per file
directory.files.each do |file|
end.each do |file|

The reason is that the list of files might be large. Really large. Eat-all-your-RAM-and-ask-for-more large. Therefore, every time you say files.each, fog makes a fresh set of API calls to Amazon to list the available files (Amazon’s API returns a page at a time, so fog works a page at a time in order to keep its memory requirements sane).

Sending it out

Alright, so you (eventually) become satisfied enough to send it off, what is the URL endpoint to your resume?

puts file.public_url

Pop that link in an email and you should be ready to cruise job ads and send your resume far and wide (Engine Yard is hiring, so check us out!). Now you are set, unless you are interviewing for Google, or Rackspace… Both of these companies have their own cloud storage services, so using Amazon S3 might not be the foot in the door you hoped for.

More clouds? How much extra stuff will you have to do for these services!?! Hardly anything needs to change, you just have to pass slightly different credentials in, but I’m getting ahead of myself.

Google Cloud Storage

Sign up here and get your credentials here under the section “Interoperable Access”.

connection ={
  :provider                         => 'Google',
  :google_storage_access_key_id     => YOUR_SECRET_ACCESS_KEY_ID,
  :google_storage_secret_access_key => YOUR_SECRET_ACCESS_KEY

Rackspace CloudFiles

Rackspace has Cloud Files and you can sign up here and get your credentials here.

connection ={
  :provider           => 'Rackspace',
  :rackspace_username => RACKSPACE_USERNAME,
  :rackspace_api_key  => RACKSPACE_API_KEY

If you work with the European cloud from Rackspace you have to add the following:

:rackspace_auth_url => ""

Then create, save, destroy as per fog-for-AWS. The :public => true option when creating directories (see above) is important for Rackspace; your folder and files won’t be shared to Rackspace’s CDN and hence your users without it. Similarly the :public => true on files is important for AWS and Google or they will be private.

Local Storage

While you are working out the kinks you might not want to do everything live though, ditto for while you are running tests, so you have a couple options to try before you buy. First, you can use a local provider to store things in a directory on your machine.

connection ={
  :provider   => 'Local',
  :local_root => '~/fog',
  :endpoint   => ''

Note that endpoint is optional. Files will be stored in the location contained in local_root and if endpoint is present, they will have a public_url. According to the options hash above, a file stored locally as ~/fog/pictures/kittens/gorbypuff.jpg will have a public_url of If you leave off endpoint from the options hash, your files will have a public_url of nil

A situation where this is useful is where you are testing an Uploader class in a Rails application using Local Storage. If you set

:endpoint => Rails.root.join 'tmp'

then your files end up having a public_url that is a path on your filesystem under Rails.root.join 'tmp'. You can then conveniently test methods that use public_url by working within your local filesystem.

Mocking out Cloud Storage

Of course when you are testing or developing you can always just use the mocks (at least for AWS and Google, Rackspace still needs mocks implemented if you are looking for somewhere to contribute). They emulate the behavior of the external systems without actually using them. It is as simple as:

connection =

Cleaning up

Fog takes care of the rest so you can focus on your cover letter. And with the awesome cover letter and cloud delivered resume you are probably a shoe-in. So all that is left is to cleanup that leftover job hunt residue.


Checking if a file already exists

Sometimes you might want to find out some information about a file without retrieving the whole file. You can do that using ‘head’.

#returns nil if the file doesn't exist
unless directory.files.head('resume.html')
   #do something, like creating the file

#returns a hash with the following data:
# 'key' - Key for the object
# 'Content-Length' - Size of object contents
# 'Content-Type' - MIME type of object
# 'ETag' - Etag of object
# 'Last-Modified' - Last modified timestamp for object
puts directory.files.head('resume.html')


All done. Try out all the different options and let me know if you have any bugs or issues. I also wrote up a more consolidated example as a script that you can use for reference.

Bonus, note the Fog.mock! command. In your tests you can easily mock out calls to cloud providers.

Please let me know in the comments if you got a new Ruby job because you hosted your CV on 3 different Cloud Stores without getting your hands dirty.

Have questions or comments? Hop into #ruby-fog on freenode, ping @fog or @geemus.

And please always remember that I accept high fives and contributions!