Skip to content

esenator/recipes

Repository files navigation

recipes

Ethan Senator and Ana Bealo

Recipes is a social cooking app where users post recipes online. Other users can then view these recipes and if they like them, can cick on the poster's profile from the recipe page to view other recipes that that poster has made. Eventually, users will be able to "fork" recipes, which will allow them to create variations by autopopulating a new recipe with the information from its parent which can then be customized, all while keeping a record of that parent chain so that viewers can follow a recipe back to its original. This functionality is in our database, however, we have not yet built a way to edit completed recipes, so we haven't activated the forking functionality yet. We also plan on letting users follow other users, again this functionality exists in the database but has not yet been implemented.

Sight overview

New users can create an account via the sign up page, the only required fields are username and password, which we hash and salt before adding to our database. After logging in, the user is redirected to the index page which currently shows their username and the make new recipe button. Users can navigate the site with the navbar, which has all the relevant links including the profile view. When making a new recipe, if the unit or ingredient the user uses is not in our database, we use ajax to add it to the database so that future recipes can be made more efficiently. Recipes autocomplete units and ingredients from the database. Users can add steps to the database using our inline rich text editor, formatting it however they like. If a user wishes to browse through recipes they can go to the browse tab to view an overview of all the recipes, or use our search tab, which currently searches for all recipes that contain a given ingredient. Currently, any error that occurs brings the user to our error page, which shows a log of all errors as flashed messages.
Most of our source code is in the Recipes subfolder, the only ones outside that are our generated files for running the project on Azure, the database control python files, and our configuration and run python files.