All right, so after all of that big old explanation, probably more than you wanted to know, I'm going
to press enter.
We're going to do this.
So the first thing that's going to do is, uh, say allow to that it's going to say unable to find image
locally.
So I don't have this image, this blueprint running on my computer.
And so it's now fetching it from Nanaimo, this, this place right here that we gave it.
And it's downloading the, this, this Docker image coming into this computer.
And you're seeing all of this downloading.
And I've got a medium internet connection.
So it's quite fast.
It might be slower for you as it downloads onto my computer.
This this image this blueprint from and it ends websites.
And when it's done with that, it's going to be time for it to create a running Docker container on
my computer running this software that's being described here.
And you can see it's got about 30s to go.
So I will see you in a second.
Okay.
Well, it just completed really fast.
It downloaded it and it then got started.
It then said migrations in Progress.
It gave all of this stuff like lots of lots of reports that you may not have gotten, because you will
have created this at a slightly different time to me.
And then it has this, and then it has a message.
Failed to start Python task runner in internal mode.
Because Python three is missing from this system.
It angrily tells me.
And now you might read that and you might say, well, that's not true.
I've got Python three on my system.
Or maybe you don't have it, but if you do, then you're probably thinking that.
To which the answer is aha!
It's misleading this message when it says it's missing from this system, it's not actually referring
to your computer confusingly.
So what is it referring to?
It's referring to the Docker container, the computer within the computer.
And it's saying that it's running this this instruction before Python three got installed.
And what you need to think when you see this kind of message is that, look this container was created
by Pn10.
That means every time someone starts it like this on any computer anywhere, they're going to get this
message and that must mean that are doing it on purpose.
They know what they're doing.
They built this container intentionally.
We don't need to worry about that message.
Obviously, they intended for Python three to be missing.
And it says here the Python runner in internal mode intended only for debugging.
So none of this matters is my guess.
And this next message also doesn't matter is my guess.
It ran, it successfully ran and it now says it's accessible via localhost.
Press O to open in the browser.
But I have news for you.
If you press O, nothing is going to happen.
You might think, why?
What's going on?
What?
Well, it's the same catch again.
A pressing O would open it in a browser within this Docker container, which is in some little world
somewhere that is, that is built within our computer.
We want to open a browser on our actual computer.
You sometimes call it the host when you're speaking in Docker language.
So so we can't we can't do that from this, this command which is now within the the container.
Uh, so but it says inside the container that the editor is now accessible on this web address.
It's running in localhost five, six, seven, eight.
And again, if we bring up a browser and we go to localhost, that's not the same as the container's
localhost.
But do you remember with apologies that this is getting to, to uh, detail for you, this thing here,
this five, six, seven eight has been mapped between the Docker container and the outer world, which
means that we would indeed be able to bring up a browser pointed at five, six, seven, eight.
And it's going to show us whatever is on that port on our container.
That might not have made it much sense to you.
And it doesn't matter if it hasn't.
Just just know that we should be able to bring put that into a browser window and see it come up, which
is what we're just about to do first.
Just before we do that, I do want to quickly show you Docker desktop one more time.
Okay, so here I am on Docker desktop and I'm on the containers page.
And I just want to show you.
You remember on volumes page we have this data uh, and uh there it is.
But if we go to the containers page now you'll see we have a new container.
Remember, this was empty a second ago.
Now it has a container called N810, and it has like an ID.
It's the image, the thing that was used, the blueprint that was used to create this container is this
thing here, which you remember was in our command.
Uh.
And look at that.
It's telling us, just as I just explained to you, that port five, six, seven, eight inside that
container is being mapped to port five, six, seven eight on the computer overall.
And so these two ports are connected together in some way.
Uh, and uh, yeah, if I click on images, this is like the list of blueprints.
You can see that we've got this this image, this description of how one goes about creating this container.
It's all there.
Everything is set up and running on our computer.
It is on mine and hopefully on yours.
And all that remains is to open up a web page and go to localhost.
Colon 5678.
Okay.
Let's do that.
Let's go back to the browser.
Here it is a new browser window http localhost colon 5678.
Here we go.
Wow check that out.
Ha.
We we have ourselves an innate n screen set up owner account.
What is this about?
Well this is setting up like your login to your own version of Nh10 running on your own computer.
So and this will be stored in a database running in that Docker container on your computer.
We're now calling into that Docker container.
So this is nothing to do with an cloud.
Now, this is not the user account that you're already set up before.
This is just something for your own database.
So you can go to town here.
But but it's worthwhile putting in a proper email because as you'll see, they they like to send some
information.
So I'll put in my name, I can spell it and then put in some some fancy password.
I will copy a password, generate password.
Thank you.
Copy password.
So put in a password there.
And I don't want to receive security product updates.
And now I will press next okay.
And all these things come up.
We might as well keep that keep track of that so we can log in again.
And then they want to, uh, follow all of this.
But it turns out you can just press, get started and miss it all, uh, get paid features for free
forever.
So this this, uh, it's already for free forever.
Uh, these these features are little nice extras.
And the reason they're doing this is to make sure that they get your email address, I think.
But you might as well, because it's good to have these things.
You can read about what they give you.
So if you say send me a free license key, then when you do that, you will get an email very shortly
and it will tell you how to then put in that.
And that way you unlock a few extra, extra features into this platform.
But here we are.
We have arrived.
This is Nw10 and it's running on our computer.
And really, if you want to be pedantic about it, it's running inside a Docker container on my computer,
and we've mapped the ports such that I can just go to localhost 5678, and it's reaching into the container
and talking to the server that's running inside that Docker container on my computer, which is running
Nw10.
And this, this with the, the menu over here, that looks pretty familiar.
This is similar to what happens when you go in to the home screen after after signing in to cloud.
The only difference is it's running right here on my computer.