What's up ya'll, welcome to Obscurify

The goal here is to show you as many interesting things about your Spotify listening history as possible, and to quantify how unique your taste is compared to everyone else.

As of now, this project contains three elements: on the backend, a few Node.js apps; and two versions of the frontend: an Angular 1.6 app for desktop browsers under the /desktop folder, and an Ionic PWA for mobile users found under /mobile.

Obscurify uses three server-side node programs to function:

• login_server handles authentication with Spotify. the "/login" endpoint is hit and the flow starts when you hit the big "sign in" button. Runs on port 8001
• spotify_data_server handles the retrieval of user data from both Spotify's (ex. your top tracks/artists) and Obscurify's servers (ex. total user count, your "current" list history, your Obscurify score percentile). Runs on port 8002
• database_server handles interaction with the three Dynamo tables, "users", "countries", and "global". Only is called by spotify_data_server. Runs on port 8003

PM2 is great for running and automatically restarting these node apps, with the following commands:

pm2 start login_server.js -- 'CLIENT_ID' 'CLIENT_SECRET' --watch
pm2 start spotify_data_server.js --'OBSCURIFY_SECRET' --watch
pm2 start database_server.js --'OBSCURIFY_SECRET' --watch

In order to hit these node apps with HTTPS calls, I followed a guide like this to set up reverse proxy, routing a request such as GET https://obscurifymusic.com/login through port 8001 where login_server.js is listening.

CLIENT_ID and CLIENT_SECRET keys are from Spotify's Developer site, OBSCURIFY_SECRET is present to ensure that only spotify_data_server can access database_server. It's a string I made up, it doesn't matter what you make it, just use the same string in both commands.

Make sure to change the redirect_uri on login_server if you want to run this yourself - and don't forget it needs to be on the list of Redirect URIs in your app's Spotify Developer page.