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

Travis CI setup for build check. #93

Closed vivek-sethia closed 8 years ago

vivek-sethia commented 8 years ago

@sacdallago I have included the Travis CI now

vivek-sethia commented 8 years ago

@sacdallago It's not passing since I am not passing the MongoDB credentials as environment variables. I am working on it.

swathi-ssunder commented 8 years ago

Finally 😌 Can we merge this now ?

sacdallago commented 8 years ago

The problem on docker persists. The problem is in the Dockerfile (or package.json, for the reference).

You can open up the build and scroll to the bottom to find out the problem:

Step 8 : RUN grunt apidoc
 ---> Running in 49d6127281a5
>> Local Npm module "grunt-apidoc" not found. Is it installed?
Warning: Task "apidoc" not found. Use --force to continue.

https://hub.docker.com/r/pokemongoers/pokedata/builds/b76pdq27zhxwazk3qwhuw6t/

Please fix :) And you can fix it by trying to build on your own machine via the dockerfile ;)

sacdallago commented 8 years ago

Yet another hint: https://github.com/apidoc/grunt-apidoc

And another hint: npm install grunt-apidoc --save-dev

I feel like Oprah just giving out hints to everyone

vivek-sethia commented 8 years ago

@sacdallago Yesterday, I did installed apidoc which was also reflected in package.json but I didn't do grunt-apidoc. I will do that now and build docker locally and see whether it works. Though docker was working locally even without this.

sacdallago commented 8 years ago

@vivek-sethia did you delete all of the previous containers+imgaes and were you actually using the version which had the dockerfile with that one RUN line? Trust me on this one: with the current dockerfile and the current package.json, this machine would have never built :) Not locally, not remotely. If it did build locally, it shoulnd't have :P

vivek-sethia commented 8 years ago

@sacdallago I have the same docker file locally and it did build and I always run all the commands for stopping containers, deleting containers, and removing images. I am myself amazed by this and that's why I am now trying to include Docker build check along with Travis. :P

sacdallago commented 8 years ago

:D Mysteries!

I also was looking for someway to make docker build on PRs and not on merges, but had no luck so far. If you find something PLEASE let me know! :D I'd love to be able to build on PRs and even better, to deploy on PRs! Just imagine... the power.....

sacdallago commented 8 years ago

@vivek-sethia P.S.: This might be a workaround https://docs.travis-ci.com/user/docker/

vivek-sethia commented 8 years ago

@sacdallago I was reading the same and writing our code for Travis. :P

sacdallago commented 8 years ago

The only thing missing there is access the running docker instance from travis... But let's check it out first, maybe travis keeps the machine running and you can access it somehow, no idea

swathi-ssunder commented 8 years ago

With reference to https://github.com/PokemonGoers/PokeData/pull/93#issuecomment-243753167 , even I built locally(on OSX) using the Dockerfile and there was no failure. There are no errors, as they are on the remote. Wierd it is 😕