推Rails應用到AWS彈性青苗和MacOSX一起

Question

目前我要去雖然亞馬遜的指令來推動一個Rails應用程序到一個新的EB實例：http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_Ruby_rails.html

每次我嘗試，我得到第14步，讓秀

無法更新本地Git配置。按照「http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/command-reference-get-started.html」的指示設置您的Git存儲庫，然後重試。

我也試過「git aws.push」，但它不適合它。

是否有可能是我有權限問題或者我的某個路徑是錯誤的？

什麼是最好的方式去調試呢？

感謝

附加信息 下面是輸出的時候我做的git aws.push

$混帳混帳aws.push： 'aws.push' 不是一個git命令。參見'git --help'。

也.elasticbeanstalk目錄是除了一個配置文件空

EB初始化返回此：

> $ eb init 
To get your AWS Access Key ID and Secret Access Key, 
    visit "https://aws-portal.amazon.com/gp/aws/securityCredentials". 
Enter your AWS Access Key ID (current value is "*****"): 
Enter your AWS Secret Access Key (current value is "*****"): 
Select an AWS Elastic Beanstalk service region (current value is "US East (Virginia)"). 
Available service regions are: 
1) US East (Virginia) 
2) US West (Oregon) 
3) US West (North California) 
4) EU West (Ireland) 
5) Asia Pacific (Singapore) 
6) Asia Pacific (Tokyo) 
7) Asia Pacific (Sydney) 
8) South America (Sao Paulo) 
Select (1 to 8): 
Enter an AWS Elastic Beanstalk application name (current value is "fooapp3"): 
Enter an AWS Elastic Beanstalk environment name (current value is "fooapp3-env"): 
Select an environment tier (current value is "WebServer::Standard::1.0"). 
Available environment tiers are: 
1) WebServer::Standard::1.0 
2) Worker::SQS/HTTP::1.0 
Select (1 to 2): 
Select a solution stack (current value is "32bit Amazon Linux 2014.03 v1.0.7 running Ruby 1.9.3"). 


Available solution stacks are: 
1) 64bit Amazon Linux 2014.03 v1.0.7 running PHP 5.5 
2) 32bit Amazon Linux 2014.03 v1.0.7 running PHP 5.5 
3) 64bit Amazon Linux 2014.03 v1.0.7 running PHP 5.4 
4) 32bit Amazon Linux 2014.03 v1.0.7 running PHP 5.4 
5) 64bit Amazon Linux 2014.03 v1.0.6 running PHP 5.5 
6) 64bit Amazon Linux 2014.03 v1.0.6 running PHP 5.4 
7) 32bit Amazon Linux running PHP 5.3 
8) 64bit Amazon Linux running PHP 5.3 
9) 64bit Amazon Linux 2014.03 v1.0.7 running Node.js 
10) 32bit Amazon Linux 2014.03 v1.0.7 running Node.js 
11) 64bit Amazon Linux 2014.03 v1.0.6 running Node.js 
12) 64bit Windows Server 2008 R2 running IIS 7.5 
13) 64bit Windows Server 2012 running IIS 8 
14) 64bit Windows Server 2012 R2 running IIS 8.5 
15) 64bit Windows Server Core 2012 R2 running IIS 8.5 
16) 64bit Amazon Linux 2014.03 v1.0.7 running Tomcat 7 Java 7 
17) 32bit Amazon Linux 2014.03 v1.0.7 running Tomcat 7 Java 7 
18) 64bit Amazon Linux 2014.03 v1.0.7 running Tomcat 7 Java 6 
19) 32bit Amazon Linux 2014.03 v1.0.7 running Tomcat 7 Java 6 
20) 64bit Amazon Linux 2014.03 v1.0.6 running Tomcat 7 Java 7 
21) 64bit Amazon Linux 2014.03 v1.0.6 running Tomcat 7 Java 6 
22) 32bit Amazon Linux running Tomcat 7 
23) 64bit Amazon Linux running Tomcat 7 
24) 32bit Amazon Linux running Tomcat 6 
25) 64bit Amazon Linux running Tomcat 6 
26) 64bit Amazon Linux 2014.03 v1.0.7 running Python 2.7 
27) 32bit Amazon Linux 2014.03 v1.0.7 running Python 2.7 
28) 64bit Amazon Linux 2014.03 v1.0.7 running Python 
29) 32bit Amazon Linux 2014.03 v1.0.7 running Python 
30) 64bit Amazon Linux 2014.03 v1.0.6 running Python 2.7 
31) 64bit Amazon Linux 2014.03 v1.0.6 running Python 
32) 32bit Amazon Linux running Python 
33) 64bit Amazon Linux running Python 
34) 64bit Amazon Linux 2014.03 v1.0.7 running Ruby 2.1 (Puma) 
35) 64bit Amazon Linux 2014.03 v1.0.7 running Ruby 2.1 (Passenger Standalone) 
36) 64bit Amazon Linux 2014.03 v1.0.7 running Ruby 2.0 (Puma) 
37) 64bit Amazon Linux 2014.03 v1.0.7 running Ruby 2.0 (Passenger Standalone) 
38) 64bit Amazon Linux 2014.03 v1.0.7 running Ruby 1.9.3 
39) 32bit Amazon Linux 2014.03 v1.0.7 running Ruby 1.9.3 
40) 64bit Amazon Linux 2014.03 v1.0.6 running Ruby 2.1 (Puma) 
41) 64bit Amazon Linux 2014.03 v1.0.6 running Ruby 2.1 (Passenger Standalone) 
42) 64bit Amazon Linux 2014.03 v1.0.6 running Ruby 2.0 (Puma) 
43) 64bit Amazon Linux 2014.03 v1.0.6 running Ruby 2.0 (Passenger Standalone) 
44) 64bit Amazon Linux 2014.03 v1.0.6 running Ruby 1.9.3 
45) 64bit Amazon Linux 2014.03 v1.0.7 running Docker 1.0.0 
46) 64bit Amazon Linux 2014.03 v1.0.6 running Docker 1.0.0 
Select (1 to 46): 




Select an environment type (current value is "SingleInstance"). 
Available environment types are: 
1) LoadBalanced 
2) SingleInstance 
Select (1 to 2): Create an RDS DB Instance? [y/n] (current value is "Yes"): Create an RDS BD Instance from (current value is "[No snapshot]"): 



1) [No snapshot] 
2) [Other snapshot] 
Select (1 to 2): Enter an RDS DB master password (current value is "******"): 
If you terminate your environment, your RDS DB Instance will be deleted and you will lose your data. 
Create snapshot? [y/n] (current value is "No"): 
Attach an instance profile (current value is "aws-elasticbeanstalk-ec2-role"): 


1) [Create a default instance profile] 
2) aws-elasticbeanstalk-ec2-role 
3) admin_role 
4) [Other instance profile] 
Select (1 to 4): Failed to update local Git configuration. Follow the instructions at "http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/command-reference-get-started.html" to set up your Git repository, and then try again. 

Answer 1

一個discussion後，我們能夠確定該問題曾與做OS X在可執行文件上放置下載隔離區。

要確認這是問題，請運行ls -al AWS-ElasticBeanstalk-CLI-2.6.3/AWSDevTools/Linux/。如果你看到@旁邊的權限，如：

-rwxrwxrwx@ 1 user staff 2134 22 Apr 00:17 AWSDevTools-RepositorySetup.sh 
drwxr-xr-x 7 user staff 238 25 Sep 14:51 scripts 

那麼你的可執行文件被隔離。

失敗是因爲當eb init試圖執行它時，執行失敗。有關此問題的更多信息記錄在here。

解決方法是運行：

$ xattr -rd com.apple.quarantine AWS-ElasticBeanstalk-CLI-2.6.3/AWSDevTools/Linux/ 

確認它不再被隔離帶ls -al，然後用eb init繼續完成設置。