0:10
Hello everyone, welcome back to my
0:12
channel Nack. You might heard about N
0:16
which is an automation platform that can
0:19
save you many hours for your manual
0:24
It also allows you to connect all your
0:27
favorite tools together in a powerful
0:30
ways. Essentially, it's an open-source
0:33
workflow automation platform, but it is
0:37
much more customizable comparing to
0:39
other platforms. It also allows you
0:44
That's why I am in this video to show
0:47
you how easy you can create your own N
0:52
instance in the cloud for free. I'm
0:54
going to use a different ways to create
0:56
it and different platform to test it.
0:59
So, hope you like it. Now, let's jump
1:06
The easiest way to selfhost nan is using
1:10
docker. But of course there's multiple
1:13
other ways to deploy it. You also can
1:16
use mpx which requires node.js to run
1:20
nam. But the easiest and faster way
1:23
which is using docker. Here's a command
1:26
which you can throw into the docking
1:28
environment. If you already have doc
1:30
environment, I would say 1 minute, you
1:33
can get this nan up and running. So now
1:42
Since we are using Docker to deploy N,
1:45
we're going to test it in this sandbox
1:47
environment. Play with Docker, which I
1:49
already introduced multiple times in my
1:52
other videos. This is very easy to use.
1:55
You can create your instance for two
1:57
hours to play with it and it's Docker
2:00
ready environment. You don't have to
2:02
install Docker. You can directly throw
2:04
the command in then it will work. So
2:07
this is two commands we can use to
2:10
deploy with Docker. Let's copy it.
2:16
They couldn't find the image. So right
2:18
away they pull it out from Docker
2:25
After probably 1 minute waiting, it's
2:28
ready to launch and the port 5678 has
2:33
been opened. We can just click list 5678
2:38
to open this map application. This
2:40
message shows up your N server is config
2:43
to use as secure cookie. So basically
2:46
they're asking us to add
2:49
this environment variable into the
2:52
configuration. So we're going to do
2:55
We're going to stop our N instance.
2:59
We're going to put the new command in.
3:04
We add this environment variable here.
3:08
Try it again. So right away 5678 port is
3:12
open here. Now we can give it try
3:19
right away. We get the set owner account
3:23
page. So what we can do? We can
3:28
put the email in and then password.
3:36
you can customize your N, but uh we
3:39
don't need to fill in any information
3:41
here. You can get started.
3:46
You also can get the free forever
3:49
version. So you just need to request
3:52
free license key. We'll skip for now. So
3:56
now your N instance self-hosted is up
3:59
and running in play with Docker this
4:06
Of course, you only can have two hours
4:10
for this instance, but it's good for us
4:13
to testing how the installation looks
4:16
like and how the interface looks like.
4:19
Let's move to another solution which is
4:23
also free, but you can run much longer.
4:30
We're going to use render this platform
4:33
to deploy an AN. The reason why is it
4:36
provides a free hobby plan. It gives you
4:40
512 megabyte RAM and 0.1 CPU and 100 gig
4:46
by free bandwidth to use. It also
4:50
support a docker deployment and you can
4:54
use your own custom domain with SSL
4:59
Only thing I think they didn't provide
5:02
it is no persistent discs free which is
5:08
required 0.25 per gigabyte per month.
5:12
Still pretty good price if you need one.
5:15
So now let's start to deploy it. You
5:18
need an account. You can use your email
5:20
address register account. After you
5:23
logged in, you can deploy a web
5:28
We're going to use in Docker. Uh we
5:30
already have a image. We just need to
5:33
paste the image link here. And later one
5:38
we used in previous deployment. You also
5:41
can find this image link here. So
5:44
connect to it. Give a name. Uh we choose
5:50
as I mentioned is give you 512 megabyte
5:54
RAM and 0.1 CPU. That's a for a hobby
5:59
You don't need to add anything here. You
6:02
can directly deploy to it without
6:05
changing any settings for the advanced
6:07
and without adding any environment
6:09
variables. So let's try deploy to web
6:15
One thing I need to remind you is the
6:18
instance will spin down
6:21
within activity. So that means if your
6:26
instance have no access to it, they will
6:29
consider there's no activity then they
6:32
will spin down. So once there's a
6:35
request coming, they're going to spin up
6:37
which going to add at least 50 seconds
6:41
or more to your instance to load the
6:44
interface for you. We can use certain
6:47
monitor application to keep accessing
6:51
the page to make it active if you need
6:54
that. But one thing you need to remember
6:56
once your instance has been spent down
7:00
because of inactivity then once you
7:03
access to it it brings up you will lost
7:05
all configuration because there's no
7:08
persistence storage here. So that's one
7:12
downside of this solution. So now we got
7:16
the URL that the link we can give it try
7:20
now it says not found. It does need a
7:23
bit time for the whole system comes up.
7:27
Well finally they got this editor is now
7:29
accessible where this link. Let's give
7:37
Now the service is fully up. You can
7:40
access it using this subdomain
7:44
from Blender to access to it. Just quick
7:48
show how to do custom domain. If you go
7:52
to settings for your project N that's
7:55
the one I created. You go to custom
7:58
domain section here. You just need to
8:03
Just need to save it. Of course, you
8:06
need to create a same name net code for
8:11
I will show you in the next deployment
8:15
to how to create your singing necro in
8:25
The final free platform I'm going to
8:28
introduce to install nan which is claw
8:31
cloud run this platform. It's completely
8:34
free as well. You can get it using your
8:37
GitHub account as long as your GitHub
8:40
account been registered for 180 days and
8:44
more and you will get free $5 credit
8:47
which is more than enough for you to run
8:50
free Nam in this cloud platform. So the
8:54
registration and how to launch
8:57
application have been introduced in my
9:00
previous video. Please watch for that.
9:03
Um this video going to focus how to
9:06
create an A application. They do have
9:10
app store which can make the deployment
9:13
much easier and simpler. You can go into
9:17
N just click on this one and then select
9:20
to it. It does require 26 cents per day.
9:26
Uh if you let it run then you exceeded
9:29
your $5 credit limitation. So your
9:34
application will be put into pause mode
9:37
after the maximum credit amount has been
9:41
reached but we will tune for it based on
9:44
our previous renders deployment
9:47
increment. It doesn't need that much CPU
9:50
and the memory. So we will make it small
9:54
size for our own to use. Once you create
9:57
the deployment in one minute it should
9:59
be completed. Uh it shows still waiting
10:03
uh but now it shows running status. It
10:06
does give you uh public IP address.
10:09
Eventually we're going to change it to
10:11
our own custom domain. I will show you
10:14
later on. Here you will see it's using
10:17
one CPU which we're going to change it
10:20
to 0.5 2 gig rand. Let me change it to
10:24
one gig. Please make the total cost per
10:28
day is 14 cent. For 30 days, it's around
10:36
per month, which is below our $5 maximum
10:40
amount we have per month. So now we
10:44
change the date. The only thing you need
10:46
to do, you just need to get it update.
10:55
While our system is creating and
10:57
learning, we're going to starting to
11:00
customize the domain. So, we're going to
11:05
copy this same name. We're going to use
11:08
our own domain which we're going to
11:14
We're going to use that and we're going
11:16
to using our cloud fair to do that.
11:25
We don't have any N record right now.
11:29
So, we're going to add a new one. We're
11:31
going to use in a C name type. And then
11:37
and then we paste Came value here which
11:43
claw.cloud deployment application.
11:47
Once you have everything ready, just put
11:52
Now we go back to our core cloud
11:55
deployment. Here we already put our
11:57
custom domain in. Let's confirm it.
12:01
Once you made change here, always need
12:06
The update will take a little bit time,
12:09
one or two minute for the whole system
12:14
The public address is still shows
12:16
pending because we are running on free
12:19
plan. So let's take a bit time. So let's
12:21
wait. So while waiting we can try to
12:24
open it to see. Well, it does work right
12:28
now. Since it is his first time to
12:30
login, we going to put our email
12:42
Yeah, we're going to request a free
12:48
You should be able to get the email
12:51
right away, maybe 10 seconds.
12:55
You also can try to activate license key
12:58
here. Um, but you may get the list
13:02
originary domain. So, we're going to
13:04
change it to our own
13:18
You also can manually activate your
13:20
community edition to get those paid
13:23
features for free. As long as you get
13:26
your activation key through email, then
13:35
So now license activated. So that's two
13:38
ways you can activate it or through
13:40
email link or through manual activation.
13:43
Once you activate it,
13:46
you should be able to refresh your
13:48
original N link. Then you should be able
13:52
to get the more features through your
13:54
interface. That's pretty much all
13:58
installation deployment method I can
14:02
show you in this video. I hope you
14:05
enjoyed it. If you do, please give me a
14:07
thumb up. Also, subscribe my channel if
14:10
you haven't. See you in my next one.
