search

felixlu / jap

Automatically exported from code.google.com/p/jap
0 stars 0 forks source link

Is any Chinese how-to guide available ? #14

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I do not speak chinese, but I can help you in english?

Original issue reported on code.google.com by morrla...@gmail.com on 15 Jan 2013 at 3:14

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I have attached screenshots of a DOTCLOUD CLI installation and an OPENSHIFT CLI 
installation.

Original comment by jeroen.v...@gmail.com on 15 Jan 2013 at 9:05

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I have attached screenshots of a JAP_WS_REMOTE_PYTHON_OPENSHIFT installation.
I will also make screenshots for a JAP_WS_REMOTE_PYTHON_DOTCLOUD installation.

Original comment by jeroen.v...@gmail.com on 16 Jan 2013 at 8:12

Attachments:

GoogleCodeExporter commented 8 years ago 
Issue 15 has been merged into this issue.

Original comment by goknmuse on 16 Jan 2013 at 11:32

GoogleCodeExporter commented 8 years ago 
I have attached screenshots of a JAP_WS_REMOTE_PYTHON_DOTCLOUD installation.
DOTCLOUD CLI is updated to version 0.9.X.
DOTCLOUD CLI 0.9.X has a problem with spaces in $HOME.
The solution:

Administrator@j3370-38e106d0f ~
$ cygpath -ws "$HOME"
C:\DOCUME~1\ADMINI~1

Administrator@j3370-38e106d0f ~
$ export HOME="C:\DOCUME~1\ADMINI~1"

Original comment by jeroen.v...@gmail.com on 16 Jan 2013 at 1:53

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
..AUTHENTICATION/USERNAME and ../AUTHENTICATION/PASSWORD in JAP_WS_LOCAL.json 
and JAP_WS_REMOTE.json is not your DOTCLOUD/OPENSHIFT username and password.
You can choose your own username and password.
Can you show me your JAP_WS_LOCAL.json and JAP_WS_REMOTE.json?

I do not know why you cannot connect to OPENSHIFT.
Is port 22 blocked? Is OPENSHIFT blocked? Are you connecting through a proxy? 
Is OPENSHIFT offline?

Original comment by jeroen.v...@gmail.com on 17 Jan 2013 at 6:52

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
You have configured JAP_WS_LOCAL.json with ex-std-node61.prod.rhcloud.com, but 
you have to configure it with ex-std-node86.prod.rhcloud.com.
I have attached ex-std-node86.prod.rhcloud.com.

I have tested your installation, and everything works :)

Original comment by jeroen.v...@gmail.com on 17 Jan 2013 at 8:32

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
- copy ex-std-node86.prod.rhcloud.com to your JAP_WS_LOCAL directory
- configure JAP_WS_LOCAL.json
REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE = 
ex-std-node86.prod.rhcloud.com

Original comment by jeroen.v...@gmail.com on 17 Jan 2013 at 1:54

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
No problem :)

Original comment by jeroen.v...@gmail.com on 17 Jan 2013 at 2:42

GoogleCodeExporter commented 8 years ago 
Hi, jeroen,
If I set REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE = ""
it works well

however, after
- copy ex-std-node86.prod.rhcloud.com to your JAP_WS_LOCAL directory
- configure JAP_WS_LOCAL.json
REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE = 
ex-std-node86.prod.rhcloud.com

it shows "certificate not ok"

DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:ClientContextFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:ClientContextFactory.getContext
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:ClientContextFactory.getContext
DEBUG:JAP.JAP_WS_LOCAL:ClientContextFactory.verify
DEBUG:JAP.JAP_WS_LOCAL:ClientContextFactory: certificate not ok
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost

[05:31] Testing Started.
    Proxy Server
    Address:    127.0.0.1:1080
    Protocol:   SOCKS 5
    Authentication: NO

[05:31] Starting: Test 1: Connection to the Proxy Server
[05:31] IP Address: 127.0.0.1
[05:31] Connection established
[05:31] Test passed.
[05:31] Starting: Test 2: Connection through the Proxy Server
[05:31] Authentication was successful.
[05:32] Error : the proxy server cannot establish connection to 
www.google.com:80
    Error = 0x05 (Connection refused).
    Please confirm that the target host address is correct.
    The error may also indicate that the proxy server is not operating properly.
[05:32] Test failed.
[05:32] Testing Finished.

Original comment by ksdaf...@gmail.com on 17 Jan 2013 at 3:09

GoogleCodeExporter commented 8 years ago 
TO  ksd...
Both fine for me.

"ex-std-node86.prod.rhcloud.com" certificate file is different for each account.

You can only use the certificate for your OpenShift account.

TO Jaroen
Finally, reviewed all I need to see for the tomorrow exams. :P
Really, gotta to sleep.

Original comment by goknmuse on 17 Jan 2013 at 4:33

Attachments:

GoogleCodeExporter commented 8 years ago 
See http://code.google.com/p/jap/issues/detail?id=18#c2 for more information.

Original comment by jeroen.v...@gmail.com on 18 Jan 2013 at 8:10

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
In JAP_WS_LOCAL.json:
REMOTE_PROXY_SERVERS/ADDRESS = jap01-chancwalter.dotcloud.com

Original comment by jeroen.v...@gmail.com on 18 Jan 2013 at 5:26

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I deploy it to dotcloud step by step, and it works finally. Thanks a lot.
But it seems very slowly in China.

Original comment by ad...@chunchu.net on 22 Jan 2013 at 8:50

GoogleCodeExporter commented 8 years ago 
OPENSHIFT should be faster in china (both DOTCLOUD and OPENSHIFT are fast in 
europe).

Original comment by jeroen.v...@gmail.com on 22 Jan 2013 at 10:03

GoogleCodeExporter commented 8 years ago 
OK, I will try OPENSHIFT tomorrow. JAP is a new choice to step over the GFW.

Original comment by ad...@chunchu.net on 22 Jan 2013 at 11:47