CPSC 455 - Assignment 5 DUE DATE: Monday, July 25 (10PM) You will submit this assignment by sending/posting the link to your deployed assignment! (We will send out a form later.) Keep your repo private Recipe Website… Complete! For the fifth assignment, you’ll be deploying the recipe website that you’ve been working on all term! It will build on the previous assignment, so start from your completed assignment 4, and begin to incorporate the requirements below. We expect you'll continue to put less time into assignments and more into the project. We’re expecting the following: 1) Deploy your recipe app by using a platform such as Heroku! (If you have not deployed anything before, we strongly suggest you use Heroku.) 2) Ensure that once your app has been deployed, you can access it on someone else’s computer, and that everything still works! (All the way from DB storage and your APIs to React, and any UI elements. All the requirements from assignment 4 must still be there.) 3) Setup a github action workflow for building your application when 1) creating a pull request to merge into any branch and 2) when merging your code into the main branch (the same workflow can be run in both situations). 4) Setup automatic deployment to Heroku whenever code is merged into your main branch (and passes the Github workflow above). You can include deploying to Heroku in the workflow (have it setup so that when you push/merge to your main branch in your assignment repo, it deploys after the build is successful), however, there are settings on the Heroku side that handle this as well, which you may use. Note: At the very minimum you should maintain the functionality based on the requirements from assignment 4. You do NOT need to maintain all of your functionality from the previous assignments (1, 2, 3), however, make sure you still have all the other technologies of the assignment, including React, Redux, Express, Node, and MongoDB! You shouldn’t need to make drastic changes to your existing code. Reminder of requirements from assignment 4: - The data should now be stored in the database. - When you add new recipes, they should be added to your database. You should be able to refresh the page, or even restart your server, and your data should persist. - Ability to delete a recipe - Additional functionality of your choice. Examples could be: - Editing an existing recipe - Filtering data from the DB - Getting details for a recipe(stored in the same table) - Getting details for a recipe (stored in a different table!) As described in the individual assignment rubric, your code will need to meet these requirements and be functional, up to perhaps a few minor glitches in tricky cases. Note that functionality includes both user-visible and console-visible issues. You should be ready to demo this to a TA during your second week lab, and should be ready to answer questions about it, as well as explain what you’ve done. HAVE FUN!!!