If it doesn't work, study the output and try to figure out what cap was trying to do when it failed. It's generally safe to attempt cap deploy iteratively. touch This should also be run as the deploy user, and will verify you have write access to the appropriate directory (the directory, such as /var/Troubleshooting We use a special github account for this purpose. If it doesn't work you'll need to authorize the deploy user to access your repository. If you are setting up a new destination: git ls-remote Run this command from the destination host, while logged in as the deploy user. Your key will need to be authorized on the gateway, on the destination, and (for some cap tasks) the user's key must be authorized on the destination. ssh ssh uname If your server is accessed via a gateway (common in some production environments), this will test your connection through that gateway. If not, update ~/.ssh/authorized_keys on the destination. ssh This should connect you to the host, without prompting for the password. Unless otherwise noted, all commands should be run from your local box. First, familiarize yourself with how SSH keys work.Īll of the tasks that cap will need to perform can be verified manually. However, if you are the sysadmin, or there isn't one in the picture, here are some pointers.
Plan A should to ask your sysadmin for access. If it is your first deploy to a pre-existing destination: If you have previously deployed this project: cap deploy Have a beer you're living the dream. Establishing this access for the first time can be a bit of a trick.
However, it can only access services you yourself have access to. 5 Signs You Need AWS Cloud Migration ConsultingĬap has made our deployments simple, fast, and reliable.
0 kommentar(er)
