小白再求有关在linux平台上的部署与发布问题

xdnabl

由于之前被临时抽去其它组帮忙WeX5的实验就停下来了。
现在项目吃紧又被拉回来背锅。。。

废话不多说了。之前的实际情况(现在也没区别)是

1。开发的APP，部署在阿里云的弹性WEB是没问题的。
2。拉到公司自己的Linux服务器上（没用任何诸如runing-php的套件，纯粹是自己的LAMP环境），数据库根本连不上。而此服务器JDK什么都装过了，版本可能旧点大概是1.6.0的，http服务是apache的，tomcat没装。说实话，实在搞不懂要装什么东西。

再来的时候发现WeX5已经升级到3.7版了。但论坛中有关linux平台的部署依旧无法找到。但从几个之前没见过的贴子中了解到，好像免费版只支持部署发布到WINDOWS平台，linux平台属于商业版？但六月的这个贴子http://bbs.wex5.com/forum.php?mo ... B%E9%83%A8%E7%BD%B2好像又可以使用runtime 方式部署,当然了，我几个月前就没找到 3.4版的 linux-runtime-php。列位如果知道哪里可以下载，请告知我一下。下载中心里3.5以上全是WINDOWS平台的软件包。

我现在的linux平台是 redhat5, redhat6, centos7，基于阿里云弹性WEB空间发布成功。现在求有关的Wex5的部署。

xdnabl

一个问题bass.php模式，可否用runtime-java进行发布？
刚刚去下载 windows-runtime-php做实验的时候，突然发现好像3.7版也只有linux-runtime-php，不知是否通用？

liangyongfei

xdnabl 发表于 2017-8-2 12:48
一个问题bass.php模式，可否用runtime-java进行发布？
刚刚去下载 windows-runtime-php做实验的时候，突然 ...

点开
http://www.wex5.com/zh-download-page/
WeX5_V3.7-runtime(for java, php, .net)
最新是3.7版本！

只有java  的 linux 版本服务器！（也就是tomcat）  

linux-runtime-php  默认没有提供的！只有windows 的 版本！

需要自己去部署！
你好楼主，
linux-runtime-php目前版本不支持，已作为产品功能建议提交(内部编号：2017080200002)，感谢楼主的支持与配合。

xdnabl

liangyongfei 发表于 2017-8-2 15:17
点开
http://www.wex5.com/zh-download-page/
WeX5_V3.7-runtime(for java, php, .net)

谢谢版主回复，但我又遇到了十分小白的问题。

win7 64位系统，下载了runtime-php-3.5
nginx 的主目录已经设置好。（数据库是远程连接外网，所以MYSQL服务没打开）
php服务和nginx服务已经打开。www文件内内容如下：
baas文件夹：common，config，lock
编译生成的文件：文件夹v-version2-zh_CN-，app.apk，app.ipa，appMetadata_in_server.json，index.html，www.zip


但得到的结果是这样的：

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.


PS：如果仅仅是用phpinfo()进行测试是没有问题的。

在WeX5的开发端生成的资源，如果仅打开php服务和nginx服务不开tomcat测试的结果也是无法打开。

请问runtime-php有无日志？接下来该怎么处理？

xdnabl

nginx的日志如下：

2017/08/08 15:19:32 [error] 11848#13772: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:19:37 [error] 11848#13772: *3 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8080/", host: "localhost:8081"
2017/08/08 15:19:52 [error] 11848#13772: *5 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:19:52 [error] 11848#13772: *7 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:19:53 [error] 11848#13772: *9 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:19:53 [error] 11848#13772: *11 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:20:32 [error] 11848#13772: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:20:37 [error] 11848#13772: *3 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"
2017/08/08 15:21:34 [error] 11848#13772: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "localhost:8081"

liangyongfei

xdnabl 发表于 2017-8-8 16:29
nginx的日志如下：

2017/08/08 15:19:32 [error] 11848#13772: *1 upstream timed out (10060: A connecti ...

错误日志 百度搜一下吧！
好像是超时了。。

xdnabl

liangyongfei 发表于 2017-8-8 17:23
错误日志 百度搜一下吧！
好像是超时了。。

但我用测试程序 <?php phpinfo();?> 反应是飞速的。。

算了。我用其它版本的系统开个虚拟机再试试吧。

xdnabl

liangyongfei 发表于 2017-8-8 17:23
错误日志 百度搜一下吧！
好像是超时了。。

我大概知道是怎么回事了，但感觉好像不太可能。。

我今天试过了从xp，2000，2003，win7，2008等系统，但最后的结果都是同一个：
单纯的phpinfo()脚本打开很快，访问生成的目标资源却无法访问——后来才确定是index.html进而是所有html文件都有问题。

我在看过2003系统的日志之后，注意到日志中出现的 upstreat:"http://127.0.0.1:8080"，然后在nginx的配置文件中找到了proxy_pass http://127.0.0.1:8080的语句，以我对nginx粗浅的认识和apache相关的配置，这个意思是访问过来之后跳转到代理指向127.0.0.1的8080端口？但我用netstat -a 后台只看到8081端口启动了服务，并没有8080端口

由于我之前自学nginx的时候用php-fpm当作nginx的php文件解释器的时候遇到过的例子：把所有的php文件都交给fpm工作9000端口去处理。那这里是不是所有的html都交给8080端口？（因为首页index.html就是html)文件，结果我新建了一个html，果然无法打开。

最后基于对Wex5开发端的了解，是不是还需要一个http服务器，如tomcat启动8080端口来解释html文件，才能使用？因为在开发端的时候，php服务，nginx服务，tomcat服务，三者必须都启动否则无法使用。

xdnabl

liangyongfei 发表于 2017-8-2 15:17
点开
http://www.wex5.com/zh-download-page/
WeX5_V3.7-runtime(for java, php, .net)

还有版主大人，你说linux暂时无runtime-php，要自己部署，那请问具体要部署些什么东西呢？

我之前完全安装的redhat6，把阿里云平台的程序拿下来，可以访问首页，但死活无法访问数据库。
据阿里云公布的信息，他们弹性WEB的后台也是linux，如果我要采用弹性WEB的方式，那又应该如何部署后台环境？


唉，现在成一团麻了。
WIN下的runtime-php部署没成功，
linux下的runtime-php不知道要部署什么环境，
linux下部署成弹性web方式环境也是一无所知。

xdnabl

对了。今天 我并没有在任何一台WINDOWS上安装JDK，使用rumtime-php方式部署是否需要安装JDK？因为我看生成了大量的.w和js文件。