-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proper way to use AWS .pem file? #31
Comments
You can use openssl_pkey_get_public to extract the pub/private keys. |
I was looking at that function before posting, it does not seem to work properly. The .pem file I have is not an x509, it is a private RSA key, like: -----BEGIN RSA PRIVATE KEY----- I've tried setting that to both the public and private key, to no avail. openssl_pkey_get_public returns false on that... |
Ok, i'll try to deploy on AWS by myself. |
So, do you have any decisions how to deploy on AWS? |
Here it is http://deployer.in/#with-pem-file 💎 |
Cool, I looked at the code you changed and it seems fairly obvious, but it doesn't seem to work for me.
But nothing actually happens. There is no password, not sure why it's prompting for that. I hit enter at the password prompt and everything completes without error, but nothing is copied or checked out. Redacted code from deploy file: <?php
require 'recipe/composer.php';
set('use_ssh2', false);
set("repository", "git@github.com:org/repo.git");
server("web", "server.aws")
->user("ubuntu")
->path('/www/repo-deploytest')
->setPemFile("~/.ssh/aws.pem"); I'm happy to contribute as necessary to make this work. |
Use 'pemFile' instead of 'setPemFile'.
|
Ah, a simple error on my part. Works flawlessly now. Thanks so much for adding this. |
Good news. Thanks a lot |
I'll make all set methods private to clearly api.
|
I'm getting the following error
|
This is deprecated, use identyFilr |
Hi, I'm trying to test a deployment with ssh + git, but I cannot figure out the proper way to use my .pem private key that lets me SSH into AWS instances. This is normally done with ssh -i key.pem or similar. I've tried setting is as both a public and a private key, to no avail. Also it seems that deployer is not properly recognizing the fact that phpseclib is failing in this case.
The text was updated successfully, but these errors were encountered: