New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add database #11

Merged
merged 1 commit into from Dec 4, 2017

Conversation

Projects
None yet
1 participant
@maecapozzi
Owner

maecapozzi commented Nov 30, 2017

Purpose

Fixes #5
Fixes #13

Currently, the application does not have a database. This prevents the addition of new features like saving songs, making recommendations based on saved songs, and building playlists. Additionally, the application was saving information in localStorage, which was fine when this was just a side project in development, but will not work in production.

Additionally, I did not have a development & a production node environment set up, so I included that as part of this PR.

Approach

I've added a development and a production database with a users table to start. I've also added the ability to findOrCreate a user upon authentication with Spotify's API. I think this gets me started collecting enough user data that I can begin to add on to it.

I've also begun storing the sessionID so that I can pull access token data accurately, rather than relying on localStorage like I have been doing.

Open Questions and Pre-Merge TODOs

  • Stop relying on localStorage before merging.

Learning

Links to blog posts, patterns, libraries or addons used to solve this problem

@maecapozzi maecapozzi added the WIP label Dec 1, 2017

@maecapozzi maecapozzi force-pushed the mc-add-db branch from e9f6f1d to 560c162 Dec 4, 2017

@maecapozzi maecapozzi merged commit 560c162 into master Dec 4, 2017

@maecapozzi maecapozzi temporarily deployed to spotify-viz-api Dec 4, 2017 Inactive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment