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!
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.
fog is distributed as a RubyGem:
Or add it in your application's Gemfile:
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:
If you are anything like me, you will continually tweak your resume. Pushing updates is easy:
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.
Alright, so you (eventually) become satisfied enough to send it off, what is the URL endpoint to your resume?
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 Storage for Developers
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.
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.
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:
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.
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.
And please always remember that I accept high fives and contributions!