Engine Yard Home

Key benefits of CLI vs. chef-deploy

Bundler Aware:

The CLI delivers improved integration with bundler, so if you are using bundler with your app, the CLI detects this and sets everything up for you.

Complete Customization:

Completely customize how deployment happens on your server. You are not limited to only hooks, but you can also change how you deploy.

Maintenance Pages:

Maintenance pages are automatically created when you are in the process of deploying. You can also manually put up and take down your maintenance page.

Immediate Feedback:

Unlike chef-deploy where you need to watch for performance problems then manually dig through logs to determine what went wrong, a CLI deploy delivers live feedback during deployment so you immediately see the cause of issues.

Easy Textmate Deploys:

With the Engine Yard Textmate bundle, you can easily deploy to Engine Yard AppCloud via your Textmate environment. Click here to download the Engine Yard Textmate bundle

Common CLI commands

ey deploy

Deploy your code on your instance without running chef

ey rollback

Roll back to the previously deployed version of your application

ey rebuild

Trigger a main chef recipe run to re-configure your systems

ey ssh

Open an ssh session to the master instance of your cluster (or the solo instance)

ey web <disable/enable>

Put up or take down maintenance pages manually

ey environments

Display a list of environments that your current application is in

ey environments-all

Displays a list of all running environments

ey logs

Display the most recent chef run log

ey recipes

Allows you to manipulate custom recipes

Get Started Now

1. Install the engineyard gem: gem install engineyard
2. Switch to your local app directory: cd ~/my_application
3. Deploy your app: ey deploy

View the CLI User Guide →