https://github.com/joshspicer/spotify-now-playing-azure

🎧 Spotify Now Playing w/ an Azure Function
https://github.com/joshspicer/spotify-now-playing-azure

Last synced: 27 days ago
JSON representation

🎧 Spotify Now Playing w/ an Azure Function

• Host: GitHub
• URL: https://github.com/joshspicer/spotify-now-playing-azure
• Owner: joshspicer
• Created: 2021-08-24T20:44:15.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-01-07T00:17:12.000Z (almost 3 years ago)
• Last Synced: 2024-10-06T18:33:11.691Z (about 1 month ago)
• Language: TypeScript
• Homepage: http://spcr.me/spotify-now-playing-azure
• Size: 52.7 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        

# spotify-now-playing (v2!)

> My AWS credits recently expired! Which means...cloud hopping.

 The successor to my [Spotify "Now Playing" with AWS Lambda](https://joshspicer.com/spotify-now-playing) website snippet.  Now hosted on Azure with Functions in Typescript (instead of AWS with Lambda in python - see [that version here](https://github.com/joshspicer/Spotify-Lambda-Functions)).

 

 See it in action on [my website](https://joshspicer.com/).

## Setup

1. Clone repo and open in either Codespaces or VSCode Remote containers

    1. This will drop you in a container with the necessary VSCode extension (Azure Functions), the required tooling (`func`), and the runtime (`node`).

    1. Run `yarn` once after any postcreate steps have completed.

1. Create your Spotify developer account and get your client secret/refresh token - like outlined in my [old guide](https://joshspicer.com/spotify-now-playing).

1. Deploy with the VSCode 'Azure Functions' extension.

    1. Select 'anonymous' access

    1. Do create a storage account

1. In the Azure Portal, navigate to your newly created storage account

    1. Manually create a table with whatever `TableName` you'd like

    1. Copy the `StorageKey` out

    1. Fill in `StorageKey`, `StorageAccountName`, and `TableName` in your Azure Function's settings (and local settings if you want to debug)

1. On the Azure Portal navigate to your Function app's "Configuration" page.

    1. Add all the secrets into your configuration by hitting the `+ New application setting` button.  These secrets are exposed as environment variables to the node application at runtime.

### Local Testing

For local testing, place all your environment variables into a file named `local.settings.json`, like so.  All of these secrets should also exist in your Function app's "Configuration".

### `local.settings.json`

```

{

  "IsEncrypted": false,

  "Values": {

    "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=.....",

    "FUNCTIONS_WORKER_RUNTIME": "node",

    "StorageKey": "...",

    "RefreshToken": "...",

    "ClientIdSecret": "...",

    "StorageAccountName": "...",

    "TableName": "..."

  }

}

```

Then run `yarn start` in the root directory.