无法将Sample Shiny App推送到Bluemix

本文介绍了无法将Sample Shiny App推送到Bluemix的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

无法将Sample App推送到Bluemix

Unable to push Sample App to Bluemix

我正在尝试使用Bluemix尝试Shiny的示例教程- www.ibm/developerworks/library/ba-rtwitter-app/index.html

I was attempting to try out the sample tutorial for Shiny with Bluemix -www.ibm/developerworks/library/ba-rtwitter-app/index.html

经历了多个问题后，我发现该应用程序未侦听Bluemix -ERROR动态分配的端口:无法在运行状况检查超时内接受连接..."

After going through multiple questions, I figured the app is not listening to the port assigned dynamically by Bluemix -ERROR : "Failed to accept connection within health check timeout..."

由于该应用程序需要cf-buildpack-r，因此可以假设环境变量也由同一包处理吗?

Since the app requires cf-buildpack-r would it be fair to assume the environment variables are also handled by the same package ?

我在哪里添加以下代码段?

Where do I add the following snippet ?

var port=process.env.VCAP_APP_PORT || 1337; http.createServer(app).listen(port), function(){ console.log('Express server listening on port ' + port); });

因为没有其他可见的js代码存在.我不确定是否丢失了一些东西.

As there is no other visible js code present. I am not sure if I am missing something.

由于没有可重现的示例来调试这种类型的错误，因此如何进行必要的修改?

How to make the necessary modifications as there is no reproducible example for debugging this type of error ?

命令

cf推送EdusasApp -b github/aruizga7/cf-buildpack-r --no-route

cf push EdusasApp -b github/aruizga7/cf-buildpack-r --no-route

我还创建了一个包含以下内容的本地manifest.yml:

I also created a local manifest.yml containing :

applications: - host: Edusas disk: 1024M name: Edusas buildpack: https:..../cf-buildpack-r path: . domain: ng.bluemix mem: 512M instances:

请帮助

推荐答案

查看文档 hub.jazz/project/crackmanworld/TwitterBluemix/overview .在项目中，有一个文件 hub.jazz/project/crackmanworld/TwitterBluemix/…包含服务器启动.服务器启动时，它将绑定到环境变量VCAP_APP_PORT中定义的端口，如果需要，您也可以使用VCAP_PORT.

Check out the project that was referenced in the docs, hub.jazz/project/crackmanworld/TwitterBluemix/overview. In the project there is a file, hub.jazz/project/crackmanworld/TwitterBluemix/… that contains the server startup. When the server starts up it binds to a port defined in an environment variable VCAP_APP_PORT, you can also use VCAP_PORT if you want as well.