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 :
/data/<appname>/shared/cached-copy. The application master then copies this (via rsync) to all the other instances in your environment.
/data/<appname>/shared/cached-copyare copied to
After your code is copied to all instances in your environment, the server-side component checks for the existence of a Gemfile.
bundle installis run on each application instance.
Gemfile.lockto ensure consistency across deployment environments.
After your application gems are installed, the server-side component
generates and symlinks configuration files and directories for your
logdirectory and more.
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.
After your application code is in place and has been appropriately symlinked, restart your application servers.
/data/<appname>/current/tmp/restart.txtto tell Passenger to restart.
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
Visit us at Neevtech.com to know more about our offerings.
© 2013 Blog | Neev Technologies