I'm six and I'm happy to be sharing this Walk through with you.

I learned what there myself through Freak Oh, Cap three years ago, and back then, I actually struggled a lot with getting my projects online at first through Cloud nine.

And then Hiroko and I only found nullify a year later and realized the deploying and scaling is a lot easier with the jab stack approach, especially with modern front and frameworks like react in view.

So this is the video Siri's I wish I had when I started out.

I hope you enjoy.

So I kind of break down the overall structure of the series into nine parts.

Don't worry, they're not all equally long, but we're going to start with the main ones first, the ones that you really need to know.

So we'll talk about nullify edge and how nullify is actually a CD and first hosting solution.

And that's why it's fast and secure and how we can upload and deploy without using any the other function audio nullify just deploying Street to see the end.

Next, we'll look into nullify build and how nullify hooks up to your get repose and continuously deploys from them.

So you have version control for your sites, but also it helps you generate your sights from static sites or any interest for maximum performance.

We understand the build process, especially how to debug it, as well as to manage the build environment with environment variables as Wells injects your tokens and secrets at Bill time.

Then we'll talk about nullified Dev, which helps you developed locally so you don't even have to deploy.

This is entirely within your local machine and the, and the idea is to make it a lot easier to test serverless functions together with your local dev environment with hot reloading as well as anything else that you might need to simulate your real production environment.

Then we'll take a look at nullify forms, and this covers the use case where you think you may need a server.

But actually you just want to have some basic form submission capability, like a comment system, people leaving a contact form or even file uploads.

And then you want to do some basic automation with that with Zapp here or a service function or other sort of Web hooks, and we'll show you how to do that in simple HTML as well.

A single page Japs and static site generators.

They were going to take a look at nullify identity, which helps you add authentication and authorization to your site, and this could be very useful for absent you commerce solutions.

And in particular, you can use a dropping widget so you don't have to call it up to you.

I or you can use something lower level that actually gives you the core functionality, and you can code you're you on top of it.

We'll also talk about authenticated functions and how nullify identity and service functions Work's work really well together as well as other things that you might want to do.

Son of people that you're working with, my actually be nontechnical users.

And you might want to edit content without going straight into source code.

And that's why I know if I has a very wonderful open source project called Nullify CMS, and we'll talk about how to set it up as well as what it does so you can validate for yourself if you want to use it or use any of the other.

Head of CMS is out there.

We're then gonna talk about Nelle.

If I add ons, which are all the other functionality of nullified.

It doesn't really fit in the other buckets above, but are still very useful, and you might want to use them on certain occasions.

And in particular, I want to shout out nullifying analytics, which are unblockable service ID analytics.

That would be very useful for your site as well as the Adam Marketplace.

When l If I starting, have Adam partners that include fauna D B, which helps you add a database to your jobs.

Excite.

Lastly, we're gonna talk about the Notify FBI where you can make your own nullify client.

For example, if the CLI and the U Y of nullify aren't exactly fitting what you need nullifies.

Platform was entirely documented, and you can go make your own client on top of it.

And a lot of users have and finally will end with pointers for learning more about nullify and jab stack and where you can get help if you run into trouble.

So hopefully that's a good overview of what we're gonna be doing today and let's start diving in.

They're a few ways to deploy to nullify now nullify drop is not the most important way, but I find it useful to explain this first because it helps explain the history of nullify.

And so is the fundamental concept of Jan Stack.

So Nelle, if I started life as a company called bit Balloon and by balloon, was a simple service where you could drag and drop like a folder on your desktop, drag it onto bit balloons, web you y, and have it be deployed immediately onto a CD en.

And to this day, that is now if I drop.

And so that is the fundamental concept of nullifying that everything that you deploy to nullify aesthetic assets and nullify takes care of deploying it on a CD en so all the points of presence around the world so that your users get them as quickly as humanly possible.

Now, Big Balloon eventually became Nell.

If I and then we dropped a bit blue and angle.

So if you go to the Euro bar and you type in big balloon dot com, you simply get redirected to act on nullify dot com slash drop.

Here you can do a simple dragon drop of your built sight, Not the source code.

The build site.

Um, and you screw around to look at the features.

We're gonna cover all of this in the rest of this video.

If you don't have a sample site nullify actually even gives one to you.

So just go see the Donald A demo.

SaiPan, that balance zip file.

And you can literally just drag and drop a zip file on two.

That drag field and you see how quickly it deploys.

There's no editing there.

It just deploys.

Live to alive, Euro, and you can scroll around.

I mean, I really don't think there is a fastest solution to getting something online.

You literally drag and drop it.

And the whole thing just deploys for you on a CD en.

So that's the fastest solution.

Now, I'm also going to try to edit this site.

I'm gonna unzip that zip file into a folder, and then you can look around.

You can see all the assets like a typical site.

Um, I'm gonna choose my favorite editor.

I use V s code.

It doesn't really matter what you use, but here in GS code, I can just drop drag and drop the file from my file explorer to V s code.

And now I have that project open.

And I can surf around and look and look at the index dot html, for example.

And this is a standard HTML sight.

Nothing.

No frameworks, nothing.

And I'm just gonna edit some of the texts to see how it shows up in instantly the poise changes.

So not receiving it.

Um, and and so I've edited that sight.

And now I can actually choose to compress that site and zip it up again to a zip file.

Um, and now I can go back to that deploy page.

And if I want to update that site, I can just go down to the Deploy section and Dragon Drop, just like I did to initiate that site.

So I just drag and drop it.

And now it's uploading.

And now it's published.

And when I click on it and hit to refresh that site, it's uploaded with the new changes.

So that's an L.

If I draw, you can always access the previous deploy with the with the unique euro.

So if you click down in here, you can access the previous deploy.

You can't even roll it back so you if you want you can just say published Deploy.

And now, when I refresh this original euro, refresh it.

It goes back to the original version because every single deploys immutable So you can always roll back something if you need to.

We don't expect you to drag and drop every time.

So the next method I'm gonna cover is using the nullify cli.

This is a pretty big topic that actually deserves a separate video.

But here we're only gonna use another feisty alive to deploy.

So I'm gonna go back to the folder that I had, which which I'm anything in the final in.

And I could call up the terminal in V s code.

I already have the nullify cli installed, But if you need to, you can run in P m install Louisville Gotta fight bashed Eli, and that will install for you.

I'm running in Nephi version of to dock 12.

You can run nullify status to check If your long did I am and you can run log in knows I log in.

If you're not.

Now I'm gonna edit my HTML again to indicate that I'm using enough.

I'm deploying from the nose.

I see a lot.

I'm just gonna say it nullifies your life rules.

So we'll see that if we should see that if we deploy, So don in here, I'm gonna write a little fly deploy for brevity because this is a lot to type.

You can actually use NTL and we'll see what we get.

So the first thing that tells me is that this folder isn't linked to the site.

Um, I don't I haven't existing site that I that I want to link to, uh but we'll avoid that for now.

And just create a new site and we'll do the linking leader.

So we're creating configuring your sight.

They will ask you to pick your teams more.

It's likely that you'll just have one or two teams.

So just pick the appropriate team and then you can pick something like nullify demo site.

Now it's asking you for the deploy path.

In most cases, you can just go with whatever suggested, but we'll talk.

You will tell you how to how to configure this leader.

And so now it's uploaded all of these pieces of information and actually showed you what it's done.

It's always given you a girl where you can actually go check it out.

So here, because I've only I've only chosen nullify deploy by the fault it deploys to a draft.

You are so you can see what it looks like in production before you actually push it to Master.

If you're happy with this and you actually want to push it to master, just run it will find deployed dash, dash Prague.

Um and that's that does exactly the same.

Thing is now if I deploy but it pushes it directly instead of a draft, your ally pushes it directly.

So here we have a live europe.

So if you click this, uh, we should be able to see the CLI rules on the means on the main euro instead of the draft Europe again remember that each of these deployments is immutable, so you can roll back to it or give uh, give this as a link to a friends or colleagues for reviewing whatever content or co changes.

You notice that the keys prompting me for a deploy path if you want to actually just hard coat that they're a few different ways to do it.

But the way that I would recommend is to create another find out Tom will file.

So I'm gonna exit out of this process, and I'm gonna create a number five.

So this is an example nullify dot com O that I have just saved my copy of my clipboard manager.

Um, we're gonna comment this out for now on, we're just gonna focus on the publish directory.

So the published directory is the directory that we want to zip up and send out to the Cdn.

Nullified, uh, down and hear me.

I usually use this folder, but here I'm just deploying the root folder so we can just say dot Run, Notify the plate prod and, uh, e no longer being.

And I'm no longer being asked about where my published deploy path is.

Um, of course, I can move all of the assets into a published holder.

So something like this just and I can move all of the assets.

Yeah, so now it looks a lot cleaner and I can build from a source code.

So then I would have to change my published directory accordingly to the distant folder.

So I only published anything inside of this, and anything outside of this does not get, and I can run that good.

Now, at Nellis, I we actually really encouraged using version control, and we call it get centric workflow.

So what I'm gonna do is I'm going to initiate get so get in it.

Now you notice one new folder that was created that I haven't explained yet is the dot net lo Fi folder.

It really is just a simple little Jason file that stores where you have linked what site you've linked the project too.

So, for example, if over here I run nullify status, you can actually see not just my log in information, but which site this particular folder this particular project has been linked to.

So it says, Don't hear another fireside info, and it gives me all that stuff and you can.

You noticed the side idea is an exact match state, not Jason.

So obviously this dot nullify folder, it's pretty helpful for know if I see a light to understand what, citing fling, too.

But I mean, I'll be so hopeful for an open source projects, for example, where people down within your repo might not have access to the same site.

So checking that in my confuse them However, actually checking that in for a team project is probably pretty handy, eh?

So that people don't have to set up their own sites.

It's really up to you, but I personally generally getting more.

You know, Sex holder.

It really depends on use case whether you do that.

So I've gone and getting I'm going to edit the content over here.

So we also reflect that we're deploying from get this time and we'll see what happens with that.

So now I can see you get you could have it get commit.

So files you become a better message than I have.

Um, And now we have No, we have to set up the remote nullify works with good lad bit bucket and get up.

Obviously, I am most familiar with get, huh?

So I'm gonna use that, But feel free to use whatever get provider care about.

So notify What am I calling?

I don't what a sight.

And it's like here so I can copy that.

You're all just say get mowed origin.

And now I have that went up?

I can actually say it.