I mean, I just wonder from, um, you talked about it being a path to pedagogical approach. I wonder, would you, would you advise people to do something like a git commit before they run it and then so that they've got a nice, um, git diff that shows them exactly what the changes were, that kind of, you know, So, great question.

Um, so there's actually two ways to use a command. So the, the three step version is a simplest. Um, if you run it without the automate all flag, then it configures your project and it leaves it for you to push the project. So the two assumptions about this project are one, uh, that you have specified your requirements, either using, um, requirements at text, pip amp or poetry. And then, uh, that you are using git to try to your, your project. Um, so if you run, uh, simple deploy, manage that by a simple deploy without the automate all flag, then it just configures your project. So that's ready to push to roku. Um, does your proc file, does it static file settings, uh, such as, um, config variable for debug to be false, uh, in the production version, jr is a new secret key. And so yeah, after that, you can look at your product and then do the git push command. Uh, I did one of my challenges with this was to, uh, answer the question, how, what's the minimum number of commands? And so that automate all going back to the idea of like what people want is an opinionated, um, approach to all those deployment questions. Or should debug be false? Or can I leave it true in my first deployment? Okay. I decided for this project, I'll make it false, um, by default and then show you how you can, you can make it true. Um, because, you know, those of us who have experience with production apps, the idea of debug being true in production is. Oh gosh, why would you even consider that? But for your very first deployment where you're just understanding the process, um, being able to say like, okay, it works on my screen. My local system is not working. All I get is a blank error page. If you can turn debug true on for a moment and just say, oh okay, that's what Heroku sees. Um, you can fix that. And I think there's, I think there's room to let people do that and not give them the impression that that's okay to do sometimes in production.