This Project is special in the sence that it is my final portfolio project. Its hard to believe that I am finaly here at the end of this program, looking back it was quite a journey. One thing i have learn during my time and with this project is that I am not afriat to jump in and investigate, and play around with code, becuase I know that failing, trying, testing, etc. is all part of the process. And what a process this project was. I want to mention that this project is the second attempt at the React/Redux portfolio project. My first attemp was the grandiose idea of building a recipe book. My first attempt was really flexing and showing off everything I learned and the project quickly becaome huge. There was user signup and signin, thrid party authentication, sessions, comments, likes, etc. Things with the first project was looking really good, but i ran into a few bugs at the end that i just couldn’t figure out. Even some professional Dev friends of mine got stumped! So I decided to put that on the backburner and finish it up at a later date. I started over after two weeks into the project and made a really simple verson that just met project requiremets.
For my JavaScript project i wanted to diversify my portfolio a do somehting not movie related, which is what my Rails and Sinatra project were based on. I decided to create a app for my partner who loved to cook. This app would become a recipe book that would take all his favorite recipes he finds on the internet and keep them in one place; this should score me some bonus points with him!!
For my rails project, I build off and expanded on the same idea that i used for my Sinatra project, a film database where a user can add details regarding a fim, i.e. name, director, year, genre and a discription. Once the film is created, a user can leave comments about the film. This project was but on rails, a web framework thta provides developers the tools they need in order to build a application. While every application i unique there are certain components taht can be found and is the core of almost every applicaton, such as: routing, asset management, database connections, etc. A good web frameworkd gives developers these baseline tools so that dont have to create the base application functionality for each new project.
It seems common sense to secure a users’ data. Like most people, despite warngins against it, most users will use the same username and password combination across many different websites. Because of this, we never want to store our users name and password in plain text in a database. Instead we run the password though a hashing algorithm. hashing algorithm manipulates data in such a way that it cannot be un-manipulated. This is to say that if someone got a hold of the hashed version of a password, they would have no way to turn it back into the original. In addition to hashing the password, we’ll also add a “salt”. A salt is simply a random string of characters that gets added into the hash. That way, if two of our users use the password “12345”, they will end up with different hashes in the database.
Belongs_to, Has_many, Has_many though: