Baby steps with EngineYard

admin wrote this on 26 Sep 2012

So the much awaited moment has come : the time to roll up my sleeves and get my hands dirty and deploy the Rails App onto the EngineYard stack .

As I stand at square one and look above with awe at the very sensitive and very crucial deployment , I shift my attention to the top right corner of my monitor where the clock’s minute digit just moved one step closer into the friday night , I feel humbled by the volume of stackoverflow questions that will be passing in front of my eyes tonight . Even though I’m fighting time , I realize I need the basics .

So how does EngineYard work ? What is an Engine Yard deployment ? Engine Yard docs are a blessing . Here are the steps of a deployment that goes on behind the scenes , for your reading pleasure :

1. Code fetch

2. Gem bundling

After your code is copied to all instances in your environment, the server-side component checks for the existence of a Gemfile.

3. Default configuration

After your application gems are installed, the server-side component
generates and symlinks configuration files and directories for your

4. Database migration

After default configuration has been setup, your database migrations are run with appropriate deploy hooks.

After migrations and their deploy hooks have been executed, your application symlink is created.

6. Restart application servers

After your application code is in place and has been appropriately symlinked, restart your application servers.

7. Final cleanup

If there are more than three previous releases in /data/<appname>/releases, all but the most recent three are removed. Your deployment is now finished.


Contributor : Emil Soman

References :

Visit us at to know more about our offerings.

Tags: , , ,

Leave a Comment