Skip to content
This repository has been archived by the owner on Nov 3, 2020. It is now read-only.

Technical Details

Jump to bottom
David Hacker edited this page Mar 26, 2018 · 2 revisions

The way the skill searches, downloads, and fetches the audio is very complicated because it relies on several free utilities. The basic flow of information through the skill could be summarized as this:

Request (1) -> AWS Lambda (2) -> Custom Heroku Server (3) -> User (4)

  1. The user makes a request mentioning the skill. See the summary for an example.
  2. The skill, which is being run on an AWS Lambda server, receives the query.
  3. The skill passes that query to a Heroku server that I built. The Heroku server pulls up the most relevant video on YouTube, downloads the audio into a temporary public folder and returns the link/metadata to the skill. The download process is done asynchronously (the server returns immediately), so the skill blocks until the server notifies the skill that the download is complete.
  4. The skill will then send a PlayRequest to the user's Alexa with the link to the MP3 file.
Clone this wiki locally