Now, drag and drop option is pretty cool, but one issue with that one is if I want to change something
about my project, meaning anything starting from Cyesis all the way to Joske Cryptologic, every time
I would need to make those changes.
Then again, I would need to run my local build.
And of course I would need to update that on that as well.
And it gets somewhat annoying.
So a better option would be setting up a GitHub repo, then connect our project to the repo, and then
every time we'll have some kind of change in the project, we will push those updates to the GitHub
and file automatically.
We'll pick it up from there.
Now, since this is an advanced course, I'm not going to cover how to create a up account.
As I say, not.
It is pretty, though.
And what are the basic commands that we are going to be using in this video?
If you need to study that, please just go to your search engine and within a matter of minutes you'll
find all the answers.
So I'm going to navigate to the GitHub and I'm going to create a new report.
So you here again, I'll call this temporary just because I'll delete it, of course.
So we're looking for temporary and then I'll call this a react project.
And of course, you have option, public or private.
I'm going to go with public.
And then once we create this report, what we're looking for are of these commands so we can just copy
and paste them like so now I'm going to navigate back to my project and I'll clear my integrity.
Tomorrow, I'll initialize a new IT repository.
I'll say that I would like to add everything here.
And as far as the committee, which is going to say initial online comment, OK, good, we are in good
shape.
And now of course, I'm going to clear the terminal again and then I'll just pass these three commands.
And essentially what we're doing, we're setting up that GitHub repo, the one that I just created to
be our remote YORO.
So essentially, every time we'll push some changes, they will be pushed to the curb.
And I can check that out by now beginning to get up there.
And of course, I can refresh and there is a this is my project and from here I would want to navigate
back to the fly.
And then I remember that second option, new side project.
We click here and then we look for to get up.
And then, of course, I already authorized it.
If you're doing this for the first time, I might prompt you to do that.
And then we're looking for react and then arm sorry it was time for already and then react and then
project.
I believe I was my name for Repo and there it is.
Now I have my repo so I click over here.
And then notice how we have this option of just deploying the site.
So in this case, not LFI is running the building, we're not doing that locally.
And also right away, it tells us, well, what is going to be the directory again, not a file.
Do all of that for us.
So we literally just need to click on deploy site.
That's all we have to do.
And what's really cool is that every time we'll have some kind of change will be able to push it so
they get help online from their little file, will pick it up online.
Just do the rebuild and I'll show you that in a second.
First, please understand that, of course, now the bill process will take a little bit of time because
the I doing that and while we're still on the subject, first I would want to change the site name.
So here I'm going to go with temporary and then react.
Project number two, my show, and as far as the Gocha, so the second Gotcher that I would want to
cover, you need to change in a package.
Jason, you build command where by default you'll just have a react script build.
I can tell you right away that for all the projects, I already changed that for the package, Jason.
So if you take a look at any project in the report, you'll find in a package, Jason, that command
changed where essentially you just need this.
See, I am the equal sign.
So that's what you need to add.
Otherwise, what happens even if you don't have any errors and everything runs smoothly locally when
you're using local host or when you're using the built command, if you use this continuous deployment,
you might get some weird errors.
Again, you just add this.
See, I am not equal on online.
Of course, it has added to the built command.
Now, if you want to check out the build it, go to deploys.
And you can see around here that we have the deploy already.
And of course the site is life.
So if I navigate back to my temporary project, number two, it is going to be the same cocktail's project.
But what's really cool that if I navigate back to my local project and in a source in the next jass,
for some reason I decide that, you know, body won't have this Marine background color.
It's going to have a color of red.
And I'm going to show you locally, I'm just going to right away push it up to the get up again.
I can the commands in the integrated terminal.
Or if you're using visual pseudocode, there's a faster way where you just click on the icon.
You need the message.
So say a big change.
And then, of course, I'll say that I would want to commit that and that I would want to push it up
to the gate.
Again, you can do it in an integrated terminal or you're using visual studio code.
You can do it through the Gowri.
And then if we navigate back, first of all, I can show you that I have the changes in the get up.
Of course I have BCG changed.
And what's really, really, really cool is that Nolfi is starting another build.
So Naglfar checks.
Hey, listen, there were some changes here.
They're all so beautiful.
Now I just need to rebuild the site.
And as you can see, site is ready to go.
And once I open, I don't see the change.
Interesting.
So it may never get back.
And I can see that the background is equal to the color shall be equal to read.
My apologies, Monsarrat, and let's do one more comment.
We're going to go with BCG changed to Red Mark.
So again, same spiel.
Why push it up now?
Again, we can double check and grab our fresh.
I can see that BCG change the red notice if we navigate to the identify which we have deploy now I have
the first one.
The BCG changed and then I have big change to read.
Far as you can see, every time you do something with a project, not a fight, we'll start the rebuild.
So now where you don't have to complete those manual steps, where you have the change and then you
run the build manually and then you do the drag and drop, you want to check it out.
The actual deploy just open up to deploy and then you can scroll down.
And if everything is correct, which it is, we have a site is live, so hopefully now everything works
and I can already see.
Yep, I have my background set too.
All right.
So these are two flavors we can use.
We're not far either drag and drop or we have continuous deployment option.
Just keep in mind about those two gotchas.
One year we have reactor water where we would have to add the underscore redirect.
And the second one is if we're using continuous deployment.
And by the way, this is important.
If you're using local build, you won't have issues or if you're using the continuous deployment, then
you must change your build command and you need to see I am an equal sign in front of the React script
build.