##Live-site of completed exercise: Donut Tycoon Completed Site

In this assessment, you'll build a RESTful, database-driven, HTTP server.

Congratulations! Your name was found in the will of a deceased donut tycoon. Apparently she had no next of kin, and your name was the first result on google when she searched 'booyah'. Naturally, she placed YOU as the heir to all of her donut shops before she passed. Now the fate of 'dozens' of donut shops lies in your capable coding hands. You must create an app that will allow you to manage your donut shops and keep track of employees. Donut let us down!

Time: One Day

Success Criteria:

• Build CRUD apps in Express
• Access data using an ORM / Knex
• Design and implement schemas
• Access data in datastores through joins
• Design and implement a RESTful API

Bonus:

• Write tests in a TDD style using Mocha Chai

1. Create a new project directory
2. Set up Express
3. Bonus: set up tests

Your app consists of three resources: shops, employees, and donuts.

• Shops have many donuts, many donuts belong to many shops
• Shops have many employees, employee belongs to a shop
• Employee has one favorite donut

You can change the methods for update and destroy to PUT and DELETE with jQuery if you'd like.

Shop index page

• This is your home page
• Lists all of the shops
• Has a button to the new shop page
• Each shop listing should be a clickable link to the shop show page
• Has buttons to the shop edit page and the shop delete route for each shop

Shop new page

• Has a form with form fields that match the columns in your shops table
• Submit button goes to the shop create route which creates the new shop, and goes back to the index page

Shop edit page

• Has a form that is populated with a single shop's information, based on the shop id in the route
• Submit button that goes to the shop update route which updates the shop and goes back to the show page for that shop

Shop show page

• Shows all of the details of shop including the donuts they carry (comes from the donuts table), and employees (comes from employee table)
• Has link to employee show page
• Has link to donut show page

You can change the methods for update and destroy to PUT and DELETE with jQuery if you'd like.

Employee index page

• Lists all of the employees
• Has a button to the new employee page
• Each employee listing should be a clickable link to the employee show page
• Has buttons to the employee edit page and the employee delete route for each employee

Employee new page

• Has a form with form fields that match the columns in your employees table
• Submit button goes to the employee create route which creates the new employee, and goes back to the employee index page

Employee edit page

• Has a form that is populated with a single employee's information, based on the employee id in the route
• Submit button that goes to the employee update route which updates the employee and goes back to the show page for that employee

Employee show page

• Shows all of the details of employee
• Has link to shop show page
• Has link to donut show page

You can change the methods for update and destroy to PUT and DELETE with jQuery if you'd like.

Donut index page

• Lists all of the donuts
• Has a button to the new donut page
• Each donut listing should be a clickable link to the donut show page.
• Has buttons to the donut edit page and the donut delete route for each donut

Donut new page

• Has a form with form fields that match the columns in your donuts table
• Submit button goes to the donut create route which creates the new donut, and goes back to the donut index page

Donut edit page

• Has a form that is populated with a single donut's information, based on the donut id in the route
• Submit button that goes to the donut update route which updates the donut and goes back to the show page for that donut

Donut show page

• Shows all of the details of donut including which shops carry it (comes from the shops table)