search

PokemonGoers / Catch-em-all

Now that we have tons of data about Pokemon (what they are, where they are, what’s their relationship, what they can transform into, which attacks they can perform, aso) we want to integrate it all into a comprehensive website. This website should contain sections about each Pokemon and its details. Additionally, the website should register the user’s location and tell the user how close is that the predicted pokemon to him/her. Additionally you will be incorporating the apps that were created by project B,C and D into the website. Your group will need to create automated builds and testing for this apps and use continuous integration to pull in new changes in the code repositories. Apps from projects B-D should be packaged and made available on NPM. Ideally when you completed these tasks the webapp component would integrate the apps by “requiring’ them. Here is a possible user story: when a user opens the website or the app the current location of the user will be shown. Additionally, the website/app will show automatically where the pokemons that are currently active are and where the pokemons that we predict to active in the nearest future (i.e. within half a day) will be located (all of this will be available from the app developed in project D). Hopefully, the website will be somewhat crowded by that data. Then, there needs to be a menu bar or something available (e.g. above the map or on the right side to it) that will list currently active or predicted pokemons. Clicking on one of them will make other pokemons on the map disappear, except of this clicked one. Separate web pages would allow the search and presentation of individual Pokemons and the information we gathered about them, including third party data (project A) and twitter analysis (project C)
9 stars 7 forks source link

Use https to serve application #77

Closed WoH closed 8 years ago

WoH commented 8 years ago

A secure context such as HTTPS will be required to access use the Geolocation API for our Project.

johartl commented 8 years ago

I suppose we can use a certificate from Let's encrypt.

sacdallago commented 8 years ago

Yeah, I'll do that on production, via let's encrypt or startssl, but rather the first one

gyachdav commented 8 years ago

status?

johartl commented 8 years ago

My understanding of this was that @sacdallago is going to take care of it? Is this still correct?

sacdallago commented 8 years ago

Yes. We have the domain name, I just have to buy the server, get the certificates and migrate docker cloud. My agenda says this should be done until Wednesday

johartl commented 8 years ago

How do you want to read the certificate inside the Docker container? Mounting a volume into the container and then use an environment variable to specify the location? docker run catchemall -v ~/secret:/secret -e HTTPS_CERTIFICATE=/secret/cert.pem

sacdallago commented 8 years ago

Nah: I'll just connect to the VM, install letsencrypt, get the certificate, reverse-proxy via nginx. It's what I'm doing with http://cell.dallago.us which really is http://cellmap-devel.bb5a8828.svc.dockerapp.io:2090 (adding the certificate layer via nginx is a joke).

johartl commented 8 years ago

So for requests to the API we have the client sending an https request to your nginx server which proxies the request to the CatchEmAll docker container running a node server which proxies the request to the PokeData container? :D

...

No but seriously... Sounds fine to me. Less to do on our side :)

AlexanderLill commented 8 years ago

@sacdallago is this me or should https://cell.dallago.us/ then actually work instead of showing ERR_SSL_PROTOCOL_ERROR? :D

sacdallago commented 8 years ago

@AlexanderLill I never shared a link containing HTTPS ;) for that website, https would just slow requests down. No need for the extra security.

AlexanderLill commented 8 years ago

Ah, then I misunderstood that :D My bad :)

On Oct 11, 2016 03:26, "Christian Dallago" notifications@github.com wrote:

@AlexanderLill https://github.com/AlexanderLill I never shared a link containing HTTPS ;) for that website, https would just slow requests down. No need for the extra security.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PokemonGoers/Catch-em-all/issues/77#issuecomment-252787680, or mute the thread https://github.com/notifications/unsubscribe-auth/AKkaOVcvsa-mMyM483HWPiZBfv-T1Zkkks5qyuW1gaJpZM4KDQhi .