NgSlackerToSpotify

Import CSV and Slacker Radio playlists into Spotify.

Prerequisites

• NVM
• Chrome or Chromium - ensure CHROME_BIN env var is exported

Note: Chrom* must match the version of the ChromeDriver. Firewall warnings on macOS can be fixed by signing the app.

Install

Run nvm use and then npm install.

Development server

Run npm run start for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Build

Run npm run build to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run npm run test to execute the unit tests via Karma.

Note: Runs automatically when starting the development server.

Unit test configuration is based on the following environment variables:

• CHROME_BIN

Running end-to-end tests

Run npm run e2e to execute the end-to-end tests via WDIO.

Note: The development server must be running.

Test configuration is based on the following environment variables:

• CHROME_BIN
• SPOTIFY_AUTH_TOKEN_PRIMARY - used to sign into Spotify and grant access
• SPOTIFY_CLIENT_ID - used to make api calls
• SPOTIFY_CLIENT_SECRET - used to make api calls

To get a Spotify Auth Token do the following:

1. Log into Spotify
2. Examine the site's cookies
3. The value of sp_dc is your auth token

The Spotify Client ID and Secret are located in the settings of the development dashboard.

Deploy

To build and upload (aka deploy) the project:

npm run deploy

Deployment configuration is based on the following environment variables:

• ENVIRONMENT
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_HOST
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_USERNAME
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_PASSWORD
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_PORT
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_HOME_PATH
• NG_SPOTIFY_IMPORTER__DEPLOYMENT_PROJECT_PATH

Note: ENVIRONMENT must match a value found in angular.json's configurations section.