Cap has made our deployments simple, fast, and reliable. However, it can only access services you yourself have access to. Establishing this access for the first time can be a bit of a trick.
cap [STAGE] deploy
Have a beer; you're living the dream.
Plan A should to ask your sysadmin for access. However, if you are the sysadmin, or there isn't one in the picture, here are some pointers. First, familiarize yourself with how SSH keys work.
All of the tasks that cap will need to perform can be verified manually. Unless otherwise noted, all commands should be run from your local box.
ssh deploy@destination.com~/.ssh/authorized_keys on the destination.ssh deploy@gateway.com ssh deploy@destination.com unamegit ls-remote <repository>touch [DEPLOY_TO]/var/www is specified by :deploy_to in your config file.)cap [STAGE] deploy:setupIt's generally safe to attempt cap deploy iteratively. If it doesn't work, study the output and try to figure out what cap was trying to do when it failed. By repeating that step manually, you can often discover where the hang-up is.