Cloudkibo / CloudKibo

CloudKibo
0 stars 0 forks source link

(multi backend) experiment setup of first client server #492

Closed sojharo closed 7 years ago

sojharo commented 7 years ago

After all the required work is done, we would then do experiment of creating setup for our first customer server and mobile setup.

jekram commented 7 years ago

@sojharo Let me know we would start with a server on Digital Ocean

sojharo commented 7 years ago

Should we go ahead with DigitalOcean? we would need following things:

Droplet (basic need) sub-domain (not urgently needed) SSH (not urgently)

jekram commented 7 years ago

Droplet Name: KiboChat2 IP Address: 138.197.116.147 Username: root Password: 3fc056f0581e413f

sojharo commented 7 years ago

I had started the setup on this and almost completed the setup. The only thing remaining here is the authentication setup in mongodb in which I was having some trouble as they have changed the way authentication was done. I am reading and trying to understand more on it.

jekram commented 7 years ago

OK. Let's try to wrap it up today

sojharo commented 7 years ago

We can close this issue as we had completed the setup yesterday and server is running on:

https://138.197.116.147:8443

It would show the ssl problem as it doesn't have domain name and ssl certificate associated with that domain name. Because of this, it would do problems in serving data to Android and iOS. Because android app disallows to get data from any server on which ssl is expired or not valid. for now it shows that ssl is not valid.

Learning from experiment:

jekram commented 7 years ago

Thanks.

Are you saying we cannot test?

sojharo commented 7 years ago

We can test the web application on following i.e.

https://138.197.116.147:8443/#/conference/jekram

however, with android and iOS, as they block server response if it is not on correct https i.e. certificate is not valid; we have two options to do the test:

  1. Remove current SSL code and ssl files from our application so that it only runs on http and not on both https and http.

  2. Give the above IP address any domain name using our godaddy account. Our current SSL certificate I remember are also applicable for wildcard sub domains so any subdomain i.e. test2.cloudkibo.com would work.

jekram commented 7 years ago

I prefer option two as it does not require any code change.

sojharo commented 7 years ago

I have created the document on how do we setup client each time. This is modified version of old document:

https://github.com/Cloudkibo/CloudKibo/blob/master/cloudkibo_documentation/OperationsGuide2.md

jekram commented 7 years ago

Thanks