In this video, we're going to create two secrets that are required for our application to run inside
of our digital ocean cluster.
So the two secrets we have to provide are a secret named JWT Dasch secret.
And that's going to contain a property of GW Tiki and the other one that I had completely forgot.
And the last video was Stripe Secrets.
That's going to contain a secret or a property called Stripe Underscore Key.
If you vacate where that strike comes from, member, you're going to go to a dashboard striped ICOM
on the left hand side.
We can find developers API keys and we're going to look for secret key right there.
You can click Reveal Test Key Tolkan to show your key.
So once we get that key, we're going to create our two secrets.
Remember, we create secrets from the command line.
So back at the command line, we're going to use QCT T.L. to access our digital ocean cluster.
That means we need to make sure that our QC, T.L. is configured to use our context or digital ocean.
It a reminder on what context you're using right now, you can very easily go back up to your system
tray.
Take a look at communities and see which one you're connected to.
Alternatively, if you are not using Docker desktop, remember, you can always do a QVC T.L. config
view.
That's going to show you all the different things are running.
We can look at contexts.
I want to find my digital ocean context.
So that's my name right there.
All then do a cube CDL config, use context, and I'll paste in the name of my digital ocean context.
And that switches me over.
Now we're going to run the command to manually create a secret on our digital ocean cluster.
We'll first create the Jason Web tokin secret.
We're going to do a cube CTO.
It's create secret.
Then generic.
Then the name of our secrets, which is a JWT Dasch secret.
Then Dash Dash from Litoral.
Equals.
And now we're going to enter in our key value pair right here without any spaces.
So our key is supposed to be JWT under squawky equals.
And then whatever value we want to assign to this.
Remember, it is supposed to be a random stream of characters that are going to somehow sign our days
on Web tokens like an entry and just some random stream characters like so.
And that should be good enough.
Kate looks good.
Our second secret for the striped key.
This one is supposed to have a name of stripe dash secret and then a key of stripe key.
And then finally, our value once again is going to come from our dashboard back over here.
Tobacco over at our terminal.
We're going to do a deal, create secret generic.
The name of the secret is going to be stripe secret.
Well, then, specify from literal.
Equals.
The key that we want to set inside the secret is stripe underscore key.
And then the value of that is going to be the key.
Often for our stripe dashboard itself.
Now, once again, extremely important that you type out the secrets.
Exactly as I show it, to make sure the secrets name is Stripe's Secret.
Make sure you've got a key inside there.
Start key and a value of your secret key.
Once you've got that all put together, we'll run that and we should see that the secret was created.
OK.
So this looks good.
Now, the last thing that we really have to do before we do a quick test of merging in April request
you do a little bit of setup on ingress, engine X.
They're going to take care of that in just a moment.