Over the course of this project I have started to learn the depths of api's and databases that are needed for a website. I have learned a lot in the terms of the api with the creation of a tables to sort data and be able to store information and display the information at a later use. I got my api to work on the local host by running python main.py on my flask and actually saw the api running and showing a valid input on the website using the url prefix /api/review with the stored values of r1 with the different name, email, rating (how many stars), and the typed review. Although when I put my api into the group flask make sure everything is in the api and model folders and the in the main.py it has the necessary things to communicate to the api and main.py the flask wouldn't open up and show it. I tried many fixes like deleting it and readding it and going over the api to make sure the api had correct notation and made sure that some of the code looked correct and cross checked it with my working api. Although a problem I kept having was the constant problem with the import of flask that couldn't be resolved.
Some pictures from my Api to show different aspects of it
Technical Achievements
My technical Achievements are mainly in the Dev Ops part of the project with deploying the site on Aws. I spend a long time on Aws to try and get the server up I really knew nothing before the project so I had to learn what to do and looked at the schedule with the deployment guide. As I was deploying I got really familiar with the code and in like 1 day I knew what I had to do because I looked at the guide a lot. I knew how to go into the correct directory to kill the site, pull, then put it back up, curl the website to see it working, and even make sure the niginx was working and it the sites-available directory. It took me about 10 hours over 3-4 days to finally get in up just by searching up the errors with docker and the internal server errors and sqlite and how I had to fix that. When I finally got the site up it was amazing and I was relieved and we could finally start finishing up our project by putting our apis on the flask and though aws. With the frontend I did a lo of testing and trial and error to solve the problems and make the frontend work more smoothly, It really dosen't look to great but I got the gist of it down and would want to improve it in the furture. After I finished with the deployment I worked tried working on the frontend project and realized I still needed to do backend with the Api/database. On this past Sunday and Monday I have put in about 8 hours to try and make this Api work and I did eventually get it to work but I added information with the tables around and changed the api to be more specific and more towards my frontend part to allow reviews to be typed and then stored in a database. Then finally I have been working on this review ticket
This is part of the backend and I had a lot of trial and error
Over the course of this class I have actually learned a lot and I have actually put a lot of time and effort into this class and moving forward I want to become better with coding and creating and linking the Api and backend with the frontend. If I was to do this project again I would make sure that I get the flask up sooner on Aws and learn from the errors and problems I had before to fix and make the deployment done soon so we have more time to work on other stuff and refine our website and project. I would also like to work on my front end coding skills to improve the look of things and get a better overall understanding of the code and more ways to code.
Caleb Navarro (Dev Ops) Period 4 Yeung
My links
Our Website Front End Night at The Museum Api Video Peer Grading CPT
My Api though the Challenges
Over the course of this project I have started to learn the depths of api's and databases that are needed for a website. I have learned a lot in the terms of the api with the creation of a tables to sort data and be able to store information and display the information at a later use. I got my api to work on the local host by running python main.py on my flask and actually saw the api running and showing a valid input on the website using the url prefix /api/review with the stored values of r1 with the different name, email, rating (how many stars), and the typed review. Although when I put my api into the group flask make sure everything is in the api and model folders and the in the main.py it has the necessary things to communicate to the api and main.py the flask wouldn't open up and show it. I tried many fixes like deleting it and readding it and going over the api to make sure the api had correct notation and made sure that some of the code looked correct and cross checked it with my working api. Although a problem I kept having was the constant problem with the import of flask that couldn't be resolved.
Some pictures from my Api to show different aspects of it
Technical Achievements
My technical Achievements are mainly in the Dev Ops part of the project with deploying the site on Aws. I spend a long time on Aws to try and get the server up I really knew nothing before the project so I had to learn what to do and looked at the schedule with the deployment guide. As I was deploying I got really familiar with the code and in like 1 day I knew what I had to do because I looked at the guide a lot. I knew how to go into the correct directory to kill the site, pull, then put it back up, curl the website to see it working, and even make sure the niginx was working and it the sites-available directory. It took me about 10 hours over 3-4 days to finally get in up just by searching up the errors with docker and the internal server errors and sqlite and how I had to fix that. When I finally got the site up it was amazing and I was relieved and we could finally start finishing up our project by putting our apis on the flask and though aws. With the frontend I did a lo of testing and trial and error to solve the problems and make the frontend work more smoothly, It really dosen't look to great but I got the gist of it down and would want to improve it in the furture. After I finished with the deployment I worked tried working on the frontend project and realized I still needed to do backend with the Api/database. On this past Sunday and Monday I have put in about 8 hours to try and make this Api work and I did eventually get it to work but I added information with the tables around and changed the api to be more specific and more towards my frontend part to allow reviews to be typed and then stored in a database. Then finally I have been working on this review ticket
This is part of the backend and I had a lot of trial and error
This is my front end
Summary and Overview with Reflection
Guide for frontend and backend
Over the course of this class I have actually learned a lot and I have actually put a lot of time and effort into this class and moving forward I want to become better with coding and creating and linking the Api and backend with the frontend. If I was to do this project again I would make sure that I get the flask up sooner on Aws and learn from the errors and problems I had before to fix and make the deployment done soon so we have more time to work on other stuff and refine our website and project. I would also like to work on my front end coding skills to improve the look of things and get a better overall understanding of the code and more ways to code.