❗Please note the Go version is the complete version of this project and should be used as the default. The JS version is incomplete and should be used for fun, not an actual deployment❗

Spotify Account AWS Account(if you want to deploy it there)

Go Node NPM/Yarn package manager

These commands should work fine with Mac/Linux. If using windows they should work if you use WSL.

First thing to do is run ./beginning.sh file. If it doesn't run, run chmod 755 beginning.sh and then run ./beginning.sh again. This will make sure you have the requirements above, and install some dependencies

1. In Spotify itself, go to your Discover Weekly playlist and first make sure it is added to your library (click heart to make it green), then profile (click the three dots > add to profile)
2. Sign up for / Log in to Spotify Dev Account with the Spotify account you want to use
3. Create a new app
4. Click 'Edit Settings' button and add http://localhost:8888/callback/ to 'Redirect URIs'
   • if you end up using a different redirect uri be sure to change redirect_uri in get-new-refresh.js
5. Copy Client ID and Client Secret to go/env.go and js/env.js files

To get your refresh token, run node js/get-new-refresh.js and if it doesn't automatically open, go to http://localhost:8888

This will go through the authentication process with your account so the api has authorization to interact with your account.

Check the terminal for the refresh token

copy refresh token to go/env.go and js/env.js files.

You can do this same process if you need a new token, yuor token somehow expired, or it just isn't working.

DON'T SHARE THIS REFRESH TOKEN OR PUSH IT TO REPO it should already be ignored from git, but you may want to check to be sure. Anyone who has this key will be able to view and edit lots of data in your spotify account until a new refresh key is generated.

Note: refresh token should last forever, so you should only need to do this once. But sometimes things act weird so this is an easy way to get a new one

I used AWS, specifically their lambda functions

• Create a new function
  • author from scratch
  • python runtime
  • I used arm64 architecture because why not (this is where you would make sure you have the correct runtime if you use go)

I followed this article. Which is basically just the file aws/labmba_function.py and the commands in awszip.sh

To make this run weekly,

• add a trigger to your function
• select EventBridge (CloudWatch Events)
• create a new rule and give it a name and description
• rule type is schedule expression, and for the expression put cron(0 12 ? * TUE *)
  • this will run the function every Tuesday at 12. I made it Tuesday beacuse idk what timezone aws is pulling from (discover weekly refreshed Monday morning-ish)
• hit add and the function should be good to go

Back in your spotify-discover-yearly directory, run awszip.sh in the terminal. If you cannot run awszip.sh, run chmod 755 awszip.sh and then run awszip.sh again

Now upload the zip file (aws/awsSpotify.zip) to your lambda function with the Upload from > .zip file option.

Once complete, go to the test tab and use the hello-world template. Hit test. We just need the function to trigger, the values don't really matter.

If everything worked properly you can now go to your spotify account and check if there is a new discover yearly playlist. It should include all the songs in your current discover weekly. Check the logs (monitor>logs) to make sure there were no errors as well.

I did have some weird issues with google chrome when trying to upload the zip file. So if it's not letting you upload, try a different browser. Based on AWS pricing docs this is well under the free tier limits. So now we have easy automation for free! (or at least hopefully, check the docs to make sure pricing hasn't changed)

For those who want to play around with the code, here's some notes: For JS solution, you will need to copy the values in go/env.go into js/env.js. Then you can run node js/app.js (Again, the JS solution is not fully featured and things may not work properly. Use go solution for actual usage)

For Go solution,

• cd go
• For the first time or if you made changes to any of the go files, run go build .
  • to build for different runtimes (helpful for deploying to cloud) use env GOOS=linux GOARCH=arm64 go build . where linux and arm64 would be the params you change out
  • you can check current params with go env GOOS GOARCH
  • check list of different configs with go tool dist list
• Then you will have an executable, to manually run, you can do ./spotify-discover-yearly on Mac/Linux or ./spotify-discover-yearly.exe on Windows

This should authenticate with previously retreieved refresh token that you definitely already put in the env files. Then it will extract songs from your discover weekly playlist and put them into your fancy new discover yearly playlist.

Unless you want to remember to manually run this once a week it would be best to put on a cron job in the cloud. This process is explained below.

Todo:

• auto populate new refresh token to env file from running get-new-refresh.js
• notification of log output on run (prob just an email)