description

• Free music for everyone!
• Music by mood!
• Copyright free music for video creators!

Logan Hufstetler	Davina Taylor	Joh Humphreys	Md Kawsar Hussen	Jonathan Bernal	Sammy Lee	Xander Jake de los Santos	Kevin Brack

• Git Clone https://github.com/labs12-music-stream-selector/Front-End.git
• Run yarn in the directory of the cloned repository.
• Add .env file with the appropriate API address you are using in the root directory. (See Environment File Section of Readme)
• Run yarn start to run the React Application.

• / - Landing Page/Google Login View
• /Home - Home/Lists of the songs and music player.
• /user - Profile view, also for editing profile.

The environment file is required to run this project. The reason is because we store our API URL inside of it, and it's used all over the client for HTTP request with the Axios library. The environment file must be in the root directory of the project, outside of the /src directory. For the environment variable to be used in the project, you must have an assignment like this. Where the value is the link to the API that is being used. In our code, this can be used with the variable process.env.REACT_FE_API.

• Local Host : REACT_APP_FE_URL - This is the local host port url, optional for your local development server.
• Production : REACT_APP_FE_API - This is the production url for development server.

• HTML

• JavaScript - React is used for UI.

• CSS

• React
• React-Router
• Axios
• styled-components
• OAuth
• Knex
• PostgreSQL
• Google-Api
• Fuse

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

* If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
* Check first to see if your issue has already been reported.
* Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
* Create a live example of the problem.
* Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes,  where you believe the issue is originating from, and any potential solutions you have considered.

We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.

If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.

Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.

* Ensure any install or build dependencies are removed before the end of the layer when doing a build.
* Update the README.md with details of changes to the interface, including new environment variables, exposed ports, useful file locations and container parameters.
* Ensure that your code conforms to our existing code conventions and test coverage.
* Include the relevant issue number, if applicable.
* You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.

See Backend Documentation for details on the backend of our project.