All right, let's start to wrap things up.
So the first thing I wanna do is show you how to shut down that community's cluster.
We had created on Digital Ocean.
So when you are ready to close everything down, we're going to go back over to Digital Ocean.
We're going to first find the networking page.
We're going to find load balancers.
Well, then find a load balancer, those created right here.
We'll click on more and then you can destroy it.
Remember, you pay about ten dollars per month for this load balancer.
So when you're all done testing the stuff out.
Don't forget to delete it.
Then you also delete the communities cluster.
We'll go to Cooper Nettie's.
We'll find our ticketing cluster.
Go to more and then destroy that as well.
We are paying about 30 dollars per month for the ticketing cluster, so don't forget to destroy that
at some point.
All right.
So beyond that, let's want to give you a couple of quick notes on how you might possibly expand this
application.
The first and probably most obvious thing we should probably add in is HTP support.
Right now, we can only connect to our application over HTP.
If you want to add an HDTV, yes, you can take a look at cert manager IoE.
This is an open source library that makes it fairly easy to add in HTP s or a Cuban I.D. cluster that
is using Ingress and Genex.
The documentation is a little bit challenging to get through, but at the end of day, it is kind of
a straightforward process, as straightforward as HDD is in general.
The next thing you might try doing is adding in a new service, perhaps with email support.
So maybe after a user purchases a order or purchases a ticket, we should send them some kind of email
just to tell them, hey, you just paid for this thing.
And here's some details on a ticket you just purchased.
So we might do that by creating a new service and we might decide to use a third party e-mail provider
such as MailChimp or sent Grid or something else like that.
This new service can then listen for events around in order being paid for.
And as soon as the order is paid for, the service can send off an e-mail to that particular user.
The next thing you might add in is a build step.
So right now, all of our services inside of our production cluster are technically running in development
mode.
They're using T.S.A. Dev to actually invoke the individual services or at least the back end typescript
ones.
And the next application is still running in dev mode as well.
We could definitely speed up all of our different services by running them in production mode.
To do this, we're going to create a separate docker file for each service that is going to build up
each service in a production style.
Really, just about the only thing that needs to change.
You're going to add in a single command into each one to tell the application to build itself.
In the case of next, it's something like NPM, run, build or something like that.
And then for the actual execution command in those Docker files, you'll change it to one of the appropriate
command is generally node index J.S..
The last thing you might try doing, and this is really just for people who are expecting to work on
micro services projects very quickly or very soon with teams of other engineers, it might be nice if
we had a staging cluster.
So staging cluster would be not a production cluster, but a cluster where other team members could
test out our application.
So maybe we should create a another cluster on digital ocean.
It should use some other kind of domain name, and it should only be accessible to people who are trying
to, well, test out the application.
We might then create another branch on our GitHub repo.
And try another kind of workflow scripts to it.
We could say that whenever someone tries to push some code to this staging branch, maybe we will deploy
the application to that staging cluster.
And then other people could come and test out our application before we finally merge that code into
master.
Those are four possible ways of expanding this application.
And, of course, the most open ended one year is really add in adding in some additional services.
Apsley, feel free.
You do not only have to do something around e-mail, get out in any number of other kind of services
to our application.
All right.
So that is it.
This is by far the longest course I have ever created and I really hope you enjoyed it.
It took about two months for me to record everything.
And I recorded, on average, about one and a half hours of video per day.
You'll notice at the end, total doesn't really total up to two months times one point five.
Turns out I recorded a ton of video, ended up throwing it away.
I do that all the time for all these different courses.
Does it really was a lot of work on my side.
I really hope you enjoyed it.
Put in a lot of effort and I hope that you learned a lot during this process.
I do hope you will check out some my other courses as well in the future and in general, I hope you
have a good time with the knowledge you gained in this course.
That's it for me.
And I will catch you later.