 I'm such an idiot. I know that errors are going to happen. And so help me. I should write code that says when an error happens, what actually happened. But I was, I didn't. In my Python, I had this template not found. And now you can see here on the code, it actually says template not found, and the template is looking for, and then which file is actually requested by. If you look at the code before this, it said not found. That was it. That's all it said. And what I found was that the build script, the Travis build script, was not working. It was failing. And I was like, but why? So in a previous video I mentioned I couldn't get the Travis stuff working. The build files weren't. The Travis image wasn't working. And a bit of a Google around. And somebody on Stack Overfled said, you just want to restart your default Docker machine. So it's like Docker-machine-stop-default. And then Docker-machine-start-default. And what that does is it restarts the default Docker machine, which is kind of what you'd expect given the name of the command. And after that I could download Travis. So I downloaded the Travis image, which was about a gig and a half, I think, in the end. It was pretty sizable, this thing. So that took a while to do. So I'm sitting there kind of like, got the file, got the Travis image booted up. And I went in and I run each command, command, command. Because this is what I was seeing on the log for the Travis. It goes blah, blah, blah. I'm doing a thing. And it just says, it said, well, it was saying not found. Now, this is the interim version, which was still not building. It says template not found, sections home. And I was like, what? Why? Why? What? So anyway, I get it running, duplicate all the steps that this is going through on that Travis image. And it turns out that because it's a fresh clone, even after the NPM installed, I haven't actually run a build. So I don't actually bake out the styles and the JavaScript as part of the Travis script. And so now you can see in the Travis YAML, the last thing it does is an NPM run build to actually make the JavaScript and CSS work. And I've learned something, you know, relearned, an old lesson, which is if you actually output what the actual problem is, then you will actually discover what the probable solution will be, rather than just writing not found. I actually have slightly more meaningful messages here. Probably won't be the last time it bites me, but it did. And it took me probably a good couple of hours last night to try and get to the bottom of why it was. An embarrassingly long time. But that's what happens. So there you go. Yeah. Subscribe to the channel if you want more of these. Thank you so many. Thank you so many. No, try that again, Paul. Thank you for all the comments and all the, you know, questions and all that kind of stuff. You can get the code on GitHub and you should definitely go and take a look. You know, you can see what I'm doing. I'm just committing stuff in as I go. And it's really fun to share all this with you. So thank you for joining me. As I say, subscribe if you want to get more and I'll catch you in the next entry.