search

PokemonGoers / PokeData

In this project you will scrape as much data as you can get about the *actual* sightings of Pokemons. As it turns out, players all around the world started reporting sightings of Pokemons and are logging them into a central repository (i.e. a database). We want to get this data so we can train our machine learning models. You will of course need to come up with other data sources not only for sightings but also for other relevant details that can be used later on as features for our machine learning algorithm (see Project B). Additional features could be air temperature during the given timestamp of sighting, location close to water, buildings or parks. Consult with Pokemon Go expert if you have such around you and come up with as many features as possible that describe a place, time and name of a sighted Pokemon. Another feature that you will implement is a twitter listener: You will use the twitter streaming API (https://dev.twitter.com/streaming/public) to listen on a specific topic (for example, the #foundPokemon hashtag). When a new tweet with that hashtag is written, an event will be fired in your application checking the details of the tweet, e.g. location, user, time stamp. Additionally, you will try to parse formatted text from the tweets to construct a new “seen” record that consequently will be added to the database. Some of the attributes of the record will be the Pokemon's name, location and the time stamp. Additional data sources (here is one: https://pkmngowiki.com/wiki/Pok%C3%A9mon) will also need to be integrated to give us more information about Pokemons e.g. what they are, what’s their relationship, what they can transform into, which attacks they can perform etc.
Apache License 2.0
9 stars 6 forks source link

Docker build check with Travis CI #94

Closed vivek-sethia closed 8 years ago

vivek-sethia commented 8 years ago

Changes to Travis file for docker build check. Package.json modified for grunt-apidoc.

swathi-ssunder commented 8 years ago

Though the build passes, the output of docker logs apidev is blank.

For the same build on my local machine, I get the following output.

npm info it worked if it ends with ok
npm info using npm@2.14.2
npm info using node@v4.0.0
npm info prestart pokemongo-api@0.0.1
npm info start pokemongo-api@0.0.1

> pokemongo-api@0.0.1 start /usr/src/app
> NODE_ENV=production node app.js
sacdallago commented 8 years ago

Aren't you missing the env variables? Try node app.js instead of npm start in my opinion!

sacdallago commented 8 years ago

Stil not logging, I see. I also have no solution there, sorry!

swathi-ssunder commented 8 years ago

No problem. We are looking into this.

Meanwhile, we raised another PR( #95 ) excluding the change of passing the env variables to docker. So that if anyone wants to access the api etc., they will be able to do so, with the passing build.

swathi-ssunder commented 8 years ago

Still testing this. Hence closing the PR.