Welcome to CRUNCHfm your soucrce for live crunchy tunes!

Special thanks to archive.org for providing the crunchiness!

This app will draw from archive.org's massive collection of live recordings. At the basic level, users will be able to select a band and a year and the app will play random live recordings in a loop (like Pandora)

MVP:

No backend, users can select a band and a year. play, pause and skip next buttons.

Bronze:

Users can select multiple artists and multiple years.Add backend (express with mongoDB) which will make api calls and pass info to front end.

Silver:

Add logic for like / dislike (if user dislikes a band maybe take that out of the search criteria)

Gold:

add users. as app moves from one song to the next, users can like a song which will add it to a playlist that * they can then replay at any time.

This project was bootstrapped with Create React App.

Folder Structure

After creation, your project should look like this:

my-app/
  README.md
  node_modules/
  package.json
  public/
    index.html
    favicon.ico
  src/
    App.css
    App.js
    App.test.js
    index.css
    index.js
    logo.svg

For the project to build, these files must exist with exact filenames:

public/index.html is the page template;
src/index.js is the JavaScript entry point.

Available Scripts

In the project directory, you can run:

`npm start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

`npm test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`npm run build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`npm run eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

jacobg1/CRUNCHfm