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
Proxy server change origin + Log level and formatting #158
This PR adds two things:
(Sorry for two separate concerns in one PR but these changes are really tiny and I want them to be merged as soon as possible)
Change origin for proxy requests. This fixes an error we currently see Error occured while trying to proxy to: localhost:8080/api/pokemon.
Environment variables to specify the log level for the proxy server and the log format for the request logger.
REQUEST_LOG_FORMAT=shortPROXY_LOG_LEVEL=info
I would like to merge this today so we can eliminate the change origin issue as source of error for #139.
This PR adds two things: (Sorry for two separate concerns in one PR but these changes are really tiny and I want them to be merged as soon as possible)
Error occured while trying to proxy to: localhost:8080/api/pokemon
.REQUEST_LOG_FORMAT=short
PROXY_LOG_LEVEL=info
I would like to merge this today so we can eliminate the change origin issue as source of error for #139.