- lab 12-part 2 exercise/ usage for each files
| File Name | What it does |
|---|---|
| decorator_1.py | There are two functions and wrapper functions prints out some sentences before and after the other function is called |
| decorator_timer.py | Outputs the time a function takes to execute. The function sums up numbers from 0 to 10000 |
| headline.py | Shows a headline from BBC rss feed (title, published time, and summary) without the use of template |
| headlines.py | Shows headlines from BBC rss feed with the use of template |
| headlines_if.py | Shows a headline from BBC rss feed filtered by a certain word with the use of template. The script pass the article to template via render_template. |
| hello_world.py | Prints out Hello, World! |
| hello_world_with_templates.py | Prints out hello, world! via render_template |
| if_name_test.py | prints out name which is a value that gets as string of main |
| macros.py | A websites that shows different information depends on which routes it goes |
| random_headline.py | Chooses one headline randomly from BBC articles using randint function |
| random_letters.py | Prints out random word that is between 0 to 32 in ascii code. |
| show_time.py | if the route is '/time', prints out current time with datetime function. |
| show_time_with_filter.py | if the route is '/time', prints out date and time in a specific format with datetimefilter function. It uses show_time_with_filter.html template. |
| url_for.py | Redirects users to url_for('home') when users go to /login |
| url_for_using_vs_url_for.py | Redirectts users to vs_url_for('home') prefix to /usr/253 when users go to /login |
| username.py | When a user goes to /username, it shows the user profile for that user |
| vs_url_for.py | Returns to prefix url |
| whats_my_name.py | Prints out name of the file, when the code run by interpreter |
Usage
URL : http://doc.gold.ac.uk/usr/340/
- Set last line in mytwits_mysql.py (debug=False) to run it without debug
- If you want to test it our without registration, put id = dan1, password = password1 in /login
- I’ve imported abort(401) for avoiding to make a user edit and delete other users’ twits and image
- The landing page(/) is for creating/updating/deleting/reading twits
- Go to /gallery for creating/updating/deleting/reading images
- Go to /register to create a new account
- There are three tables in the mysql database (users, twits, images). Primary keys for each is user_id, twit_id, image_id. Foreign key for twits and images is user_id. If you want to check the database structure, command
sudo mysql -u rootin CMD , put password and commandSELECT * FROM <table_name>orDESCRIBE <table_name> - Check out my git history
Requirement
- it is a flask app -YES
- there is more than one route and more than one view – YES This is the accessible route for my app
- / ,(Line 173) : renders “index.html” which is a landing page.
- / ,(Line 178) : displays the latest twit where username=username
- /add_twit ,(Line 183) : using flask-wtform, adds a twit
- /edit_twit ,(Line 196) : using flask-wtform, edits a existing twit
- /delete_twit ,(Line 225): remove a twit
- /login ,(Line 240): using flask-wtform and flask-login, validates user information and put it in a session
- /logout ,(Line 251): removes the user from the session if it’s there
- /register ,(Line 260) : using flask-wtform, gets new user’s information and post it to database
- /gallery ,(Line 283) : displays all the images in the ‘images’ table from database
- /w ,(Line 289) : render “upload.html” template which is a page to let user upload image
- /upload ,(Line 295) : get image information from “upload.html”, post it in database with description
- /add_image ,(Line 330) : adds image using flask-form.
- /edit_image ,(Line 343) : edits image
- /delete_image ,(Line 379) : delete image
** assigned route for api **
- /api ,(Line 161): shows all twits, you can edit twits by passing arguments
- /api/int:twit_id ,(Line 162): shows twits that twit_id is corresponding with the passing argument. You can edit it as well
- /image_api ,(Line 163): shows all images, you can edit twits by passing arguments
- /image_api/int:image_id, (Line 164): shows urls of the images that image_id is corresponding with the passing argument. You can edit it as well
- the html is rendered using jinja templates -YES all the html files in the templates is rendered using jinja templates
- the jinja templates include some control structure(S) e.g. if/else, for/endfor – YES
- mytwits_mysql.html : for/endfor (Line 5~13)
- add_image.html : if/endif (Line 11~18)
- gallery.html : for/endfor (Line 4~12)
- add_twit_mysql.html : if/endif (Line 11~18)
- edit_image.html : if/endif (Line 11~18)
- index.html : if/endif (Line 13
19), for/endfor (Line 410) - register.html : if/endif (Line 12
19, 2431, 48~55) for/endfor is inseide if phrase - edit_twit_mysql.html : if/endif (Line 11~18)
- timeline.html : for/endfor (Line 4~12)
- login.html : if/endfor (Line 12
19, 2432, 37~44) - base.html : if/endif (Line 25
32) for/endfor (Line 1823)
- it includes one or more forms – YES in forms.py, addTwitForm, editTwitForm, loginForm, RegistrationForm, UploadForm, editImageForm
- the forms have some validation -YES For form, I used flask-wtform for form validation. For login, I used flask-login for login/session validation
- there are useful feedback messages to the user – YES
-
For password when login, flask-login form has error handling (in mytwits_mysql.py line 340, forms.py line 21 & login.html line 15, 28, 40)
-
When the static file is already made, upload() prints error message in mytwits_mysql.py line 304
-
All the forms is basically offering error handling
- it has a database backend that implements CRUD operations (the database can be mysql or mongodb) -YES I’ve used SQLAlchemy.
- the create & update operations take input data from a form or forms – YES, throughout the app(/add_twit, /edit_twit, /upload, /edit_image) in mytwits_mysql.py
- there is user authentication (i.e. logins) – YES (in user.py line 10)
- the login process uses sessions -YES I’ve used flask-login, and it uses session
- passwords should be stored as hashes – YES it uses hash and salt and it encrypted with sha-512. (passwordhelper.py )
- there is a way to logout – YES there is /logout route
- there is a basic api i.e. content can be accessed as json via http methods – YES, please refer to number 4 above
- it should be clear how to access the api (this could include comments in code) YES, please refer to number 4 above