Adding a CMS to Your Flask Web App Transcripts
Chapter: Logging activity
Lecture: Logging motivation
0:00 Let's talk about logging our CMS actions. There's actually two levels that we're going to cover first.
0:06 Your site. If you're adding this to an existing site, probably already has logging. If it doesn't,
0:12 I'll show you some cool log in libraries and how we're using them. And then you can plug into those.
0:16 So here's the log from talk Python training that I talked about one out of him We get all sorts of information about what people are up to,
0:25 who has done what we could go back and look, you know, somebody sends us a message and say,
0:29 Hey, I did this and it didn't work the way expected are or something like that. We go look in the logs and see what it was.
0:35 They did So here There's a little bit of a a little bit of history of people using the A P I using the mobile APs on it looks like IOS.
0:43 A couple of people on Iowa's here requesting some information by the courses,
0:47 you know, like refreshing their list of courses or logging into their app or something like that. Right? So we have this kind of stuff going on in our
0:56 Web app, presumably right? Presumably. If not, you can add it. But we also want to add this for the CMS to know who's taking the admin
1:05 actions. And then the second layer Here is the markdown subsystem, the markdown templates, sub templates. That thing has its own logging,
1:15 and we can extensively plug it into our file logging or whatever type of logging system
1:21 we're doing. We can plug those in together so they make sure they go to the same place. For example, on training Doc, talk by thunder out of him.
1:28 We have rotating logs that show you. Here's the log for that day, and then the next day it automatically creates a new file and puts it in there
1:36 Right? So we want to take the functionality from markdown sub templates. M plug it into that system so it's all unified in one place,