This article is about Codeship Basic.

Deploy To Engine Yard

You will need about one minute to read this article.

Deploy to Engine Yard

To setup an Engine Yard deployment on Codeship, first create a new custom script deployment. From there you can call our Engine Yard deployment script.

Set EY_API_TOKEN as an environment variable in your Project Settings.

\curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/deployments/engine_yard.sh | bash -s

Custom Deploy to Engine Yard

To customize the deployment, first create a new custom script deployment. From there you can add any commands you need, including installing and calling the Engine Yard CLI.

Set ENGINEYARD_API_TOKEN as an environment variable in your Project Settings.

gem install engineyard --no-ri --no-rdoc
ey deploy --api-token "${ENGINEYARD_API_TOKEN}"

Engine Yard has additional CLI documentation if you need to further customize your deployment.

Common Errors

Engine Yard CLI is not installed by default

If you don’t have Engine Yard in your Gemfile you need to install it first. Simply add the following command to a script based deployment.

gem install engineyard --no-ri --no-rdoc

Need more help?

Contact our support team or post on Stack Overflow using the tag #codeship. Did you check the status page and changelog?

There are also several code examples and sample projects available for you to get started with.

Article not helpful?

Does this article need improvement? If so, please send feedback or submit a pull request!