Back to Parent

Process

This project built off of previous weeks' tutorials from Programming for Online Prototypes).  I reverse-engineered additional parameters for fitness information, and then used sample code provided by Daragh Byrne to work with the Giphy API.  I implemented a gem called "business_time" that I had found in an earlier discovery to keep track of the gym's hours of operation.  The files were uploaded to a local Github repository and then pushed to the cloud.

Originally, I only had the daily workouts, which combined muscle groups where applicable.  I later chose to separate the routines into their own hash in case the user wanted to look up individual muscle groups and customize their own routines.  The Giphy API, despite following a tutorial, ended up being the most frustrating part because I could see the link show up when I tested locally but I didn't see it deploying in on Heroku.  Another user ended up having the same problem, and it turned out to be related to the size of the .gif being sent, although I also had invalid url problems at first.

As with previous weeks, the user must sign up at https://pacific-scrubland-87437.herokuapp.com/about and enter their number once the secret code has been given.  There is limited interface within the website post-signup; the purpose is to have users send texts to the bot once they sign up.


Content Rating

Is this a good/useful/informative piece of content to include in the project? Have your say!

0