It's been about 15 or 20 minutes for me, so I'm now going to open up a new browser tab and try to navigate
to my application at ticketing app Braude Dot, X, Y, Z.
I can open up a new browser I can to navigate over there.
And lo and behold, the application actually appears awesome.
Now, as you can see, I've kind of recorded this video once or twice before.
So there already is a ticket here that I have created.
Well, once I'm here, I can definitely tried to create a new account.
I should be able to sign up with the new account.
I should then be able to sell a ticket.
I could put in something like.
Football match.
Twenty bucks.
And there is my ticket right there, I can view it and attempt to purchase it.
I can get up that striped window.
One of my fake credit card number, because our stripe account is still in test mode.
And that I should be told that everything is good to go.
Yeah.
There you go.
There's my ticket complete.
So that is pretty much it.
Our applications now deployed to now if we ever want to make a change, the process.
Well, we've gone through it several times now.
We're going to make some changes on a branch.
Push those up to get hub.
Make a pull request.
Merge that into M..
As soon as we do, our new images will be built and applied to the cluster.
That's it.
That's how we make changes over time.
That is pretty much it for this chorus.
That is all the topics we are going to go over, but I'm sure you might be curious about how he can
expand this application because, well, you were definitely kind of light on the styling side.
We never really built in the idea of some transferable information about tickets.
In other words, when you purchase a ticket, nothing really happens beyond saying, hey, this is now
assigned to you.
So there might be some features you want to add in.
So take out the next video.
I'm going to put in a couple of notes on some things you can expand on in this application, along with
some possible ways of implementing those steps.