Author: Toni Rib
Live Version: http://run-hacker.herokuapp.com/
This Ruby on Rails application was designed to give runners insights into any trends that might exist in their running habits. After logging in through MapMyFitness, all of a user's runs are imported along with information on location, elevation, and temperature at the time of the run.
Users can then create charts plotting distance, average speed, and/or time spent resting against temperature, elevation, location, season, and time of day. They can also view a listing of all their runs and have the ability to click on an individual run to see a map of the route and information specific to that run. The user's dashboard has aggregate information for all of their runs, such as the total distance they have run since joining MapMyFitness. The dashboard updates automatically as new runs are loaded every time the user signs into the app.
The application is hosted live on Heroku and uses background workers (redis/sidekiq) to make the API calls that import the user's data.
Click Here to See Video GIF of app
To run this application locally, you would need to obtain API keys from the following sources:
Gem dependencies can be found in the Gemfile.
If you wish to download the project and set it up locally, run the following commands:
git clone https://github.com/ToniRib/run_hacker.gitbundlebundle exec figaro install- This sets up figaro on your local machine. You will need to obtain the keys mentioned in the above section and save them in yourapplication.ymlfile.- Start Redis/Sidekiq: In one terminal, run
redis-server. In a second terminal, runbundle exec sidekiq. - While those are running, run
rails sin another terminal pane to start the actual Rails server
This test suite is written in RSpec and utilizes Capybara for feature tests, Selenium for JavaScript testing, and VCR for easy recording and playback of API calls. It also uses factory_girl for creation of objects. SimpleCov has been installed to provide basic test coverage reports.
The test suite can be run from the main directory of the project by running the command rspec. The project has test coverage at the following levels: models, workouts, services, controllers, and features.
Because this was a project for the Turing School of Software and Design and I did not want to pay for historical weather data, the application can only make 10 requests per minute to the weather API. Thus, if you are importing a large number of workouts all at the same time, it will take multiple minutes for the temperatures to get updated. However, the application will simply show "Not Available" for the temperature of any workouts until that point and those data points will not be available for plotting on the temperature chart.