We've now installed an initialized doctor.
Now we're going to use octal with a series of different commands to load up some contacts to connect
to that new cluster that we just created.
The first thing to do is install some context onto our local machine about that new cluster.
So this is the command we're going to run right here.
Dactyl Community is cluster Q config save and then the name of your cluster to get the name of your
cluster.
You can go back to the Cuban Nettie's dashboard book on Cuba, Nettie's left hand side, and it's going
to be at whatever is listed right there.
So in my case, all these simply ticketing.
So I got to run that command right there.
Back at my terminal.
And I'm going to replace that Kluster name with ticketing.
Once I run that command, I'll be told that some credentials have been added to my cube config file,
which is where all of our different context gets saved.
And then it automatically sets my context to my cluster.
So if I now issue any commands against Cubes, DTL, they will be ran against the cluster that is running
on dissolution.
For example, I can do a cube ZT.
I'll get pods.
And I'll see that absolutely nothing is running, even if I am running some pods right now on my local
machine or on my local communities, Kluster.
I can also feel that more proof here would be a get node's and that will list out all the different
nodes that are connected.
So I've got three nodes right now that are connected to my digital ocean cluster.
And naturally on my local machine, I only have one at most.
Now, of course, at some point time, we will want to swap back to our local machine context, or perhaps
if you're running everything on Google Cloud, as I showed you earlier on inside the course, you might
be or want to talk back over to that context.
So to do so, you can list out all the different contacts you have access to with QVC, T.L. config
view.
So we'll do that right now.
And that's got to list out a lot of connection information.
Well, we are really looking for here is a section called Context, but here it is right here, contexts.
And then there are a couple of options.
And each of them have a name.
That name is what we care about.
So to connect to my digital ocean cluster, that is the name or the context that I want to use if I
want to swap back to using my local communities cluster that are running on my machine.
I can either use a cluster or a contact name of Docker desktop or Docker for desktop.
Either one is fine.
So if I want to swap back to my local cluster, I'll do a QVC, T.L. config, use context and then the
name of cubes T.L..
Was it config?
Use context and then the name of Dr Desktop.
If I now do a QCT, I'll get node's.
I'll see just one note.
My doctor desktop node.
As a good reminder, if you are using debt doctor desktop, as opposed to using Docker tool box or something
like that, you can always go to that tray icon and select your contacts from right here as well.
A little bit easier.
I just want to show you the kind of behind the scenes way of doing this stuff.
I can swap back over to my digital ocean.
Do another get pods once again, no pods.
Because I'm not running anything on there just yet.
OK.
So, again, we are not going to deploy anything directly to our cluster by connecting to it and then
applying anything, we're always going to rely upon our get hub workflow.
The only reason I'm showing you how to connect directly to the cluster is that you can do some debugging,
tried to pull logs, stuff like that, so that we understand how to connect that cluster manually.
We're going to repeat a pretty similar process by creating a new GitHub workflow where we're going to
connect to that cluster that we just created by using dactyl.
We're then going to make sure that after we merge a pull request, we then attempt to apply all of our
different config files for communities, all that kind of stuff.
So quick pause and let's get started on that process in just a moment.