Your application is linked to a git repository that holds your current production code. When you deploy code it will be fetched from this repository and deployed to your instances.
If the URL to this repository is missing or invalid, you will not be able to deploy your application. Additionally, you will have issues adding instances and booting your environment.
Update your repository URL
You can configure many different applications and their corresponding repository URL and framework under Engine Yard.
- In your Engine Yard account, click on the Dashboard link.
- On the Dashboard page, click on the application you want to update.
- On the Environment page, click the pencil icon to edit your application.
- On the Application edit page, enter your new git repository URL.
- Click the Update Application button.
Test your changes first
A simple means to test your new repository URL is to try a deploy. If you have a production environment that is currently running, you can clone this environment and test your updates there before updating your production environment.
Check the deploy key
If the repository has been moved to a new account, you will need to ensure that your deploy key is installed for this repository on git. You can find your deploy key on the application page referenced in Step 4 above.
A note about SVN
Currently Engine Yard only supports git repositories for deployment. If you use SVN you can now migrate to git and continue to use your SVN workflow. See GitHub’s documentation for an example, or check the documentation for your repository provider.
If your repository URL looks like http://svn.mydomain.com/svn/myapp/trunk, then it’s most likely SVN and does not deploy as is but it can be moved to git with history with a little work.
If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.
Hi Nick, The pencil is on the Environment page and looks like this:
I modified this doc just a bit to help clarify. Hope that helps.
Thanks for your feedback! kjm
We also needed to click 'Apply' in the Environment first, otherwise deploys failed (permission denied to repo.).
Got it thanks
Please sign in to leave a comment.