Learn how NGINX is used a web server, reverse proxy, load balancer, and HTTP cache to handle the demands of high traffic sites. https://nginx.org

#nginx #100SecondsOfCode

Install the quiz app 🤓

iOS https://itunes.apple.com/us/app/fireship/id1462592372?mt=8
Android https://play.google.com/store/apps/details?id=io.fireship.quizapp

Upgrade to Fireship PRO at https://fireship.io/pro
Use code lORhwXd2 for 25% off your first payment. 

My VS Code Theme

- Atom One Dark 
- vscode-icons
- Fira Code Font
2024-02-04T06:04:38.994Z
nova-2
2-general-nova
2024-01-09.29447
30089e05-99d1-4376-b32e-c263170674af
e1f86cee-c2d4-4a7c-98d4-164b9de8bbb3
6e2444b5bf8de05d76806010976bcd80759b753aeb3607af49aee31ee0fa78f6
67875a7f-c9c4-48a0-aa55-5bdb8a91c34a
deprecated
Nginx.
It's like a gateway that stands between the Internet and your back end infrastructure.
When you visit a web app, the first place your request will go is to a web server.
Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response.
In fact, if you open up the network tab in Chrome app tools right now.
You can look at the server header on any response, and there's a good chance it'll be Nginx.
It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture.
It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance.
In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory.
You customize the behavior of your server by defining directives.
A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives.
In the global context.
We might wanna specify things like your username and where to save our error logs.
But most of your configuration will likely be done in the HTTP context.
Now one of the most important roles of NGINX is to serve out static content, like images and HTML.
We can handle that in the HTTP context, next, where we'll define 1 or more servers.
Each server is distinguished by the port that it listens to.
Nginx will keep track of every request to the server, which you can write to an access log.
The most most important thing though is to tell the server where to find the raw files, which we do in the location context.
Now when a user navigates to our domain, it knows where to find the HTML on the file system.
And we might want to set up a second location to match any image pattern to the image's directory.
Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server.
When I replace root with proxy pass, I can point to a completely different server on the Internet.
What we've created is a reverse proxy that can handle caching, anonymity, and load balancing.
This has been NGINX in 100 seconds.
Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.

Speaker 0: Nginx. It's like a gateway that stands between the Internet and your back end infrastructure. When you visit a web app, the first place your request will go is to a web server. Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response. In fact, if you open up the network tab in Chrome app tools right now.

You can look at the server header on any response, and there's a good chance it'll be Nginx. It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture. It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance. In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory. You customize the behavior of your server by defining directives.

A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives. In the global context. We might wanna specify things like your username and where to save our error logs. But most of your configuration will likely be done in the HTTP context. Now one of the most important roles of NGINX is to serve out static content, like images and HTML.

We can handle that in the HTTP context, next, where we'll define 1 or more servers. Each server is distinguished by the port that it listens to. Nginx will keep track of every request to the server, which you can write to an access log. The most most important thing though is to tell the server where to find the raw files, which we do in the location context. Now when a user navigates to our domain, it knows where to find the HTML on the file system.

And we might want to set up a second location to match any image pattern to the image's directory. Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server. When I replace root with proxy pass, I can point to a completely different server on the Internet. What we've created is a reverse proxy that can handle caching, anonymity, and load balancing. This has been NGINX in 100 seconds.

Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.
Nginx. It's like a gateway that stands between the Internet and your back end infrastructure. When you visit a web app, the first place your request will go is to a web server. Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response. In fact, if you open up the network tab in Chrome app tools right now. You can look at the server header on any response, and there's a good chance it'll be Nginx. It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture. It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance.
networking
internet
In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory. You customize the behavior of your server by defining directives. A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives. In the global context. We might wanna specify things like your username and where to save our error logs. But most of your configuration will likely be done in the HTTP context. Now one of the most important roles of NGINX is to serve out static content, like images and HTML. We can handle that in the HTTP context, next, where we'll define 1 or more servers. Each server is distinguished by the port that it listens to. Nginx will keep track of every request to the server, which you can write to an access log. The most most important thing though is to tell the server where to find the raw files, which we do in the location context. Now when a user navigates to our domain, it knows where to find the HTML on the file system. And we might want to set up a second location to match any image pattern to the image's directory. Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server. When I replace root with proxy pass, I can point to a completely different server on the Internet. What we've created is a reverse proxy that can handle caching, anonymity, and load balancing.
This has been NGINX in 100 seconds. Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.
streaming
youtube
video gaming
Nginx. It's like a gateway that stands between the Internet and your back end infrastructure. When you visit a web app, the first place your request will go is to a web server. Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response. In fact, if you open up the network tab in Chrome app tools right now. You can look at the server header on any response, and there's a good chance it'll be Nginx. It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture. It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance. In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory. You customize the behavior of your server by defining directives. A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives. In the global context. We might wanna specify things like your username and where to save our error logs. But most of your configuration will likely be done in the HTTP context. Now one of the most important roles of NGINX is to serve out static content, like images and HTML. We can handle that in the HTTP context, next, where we'll define 1 or more servers. Each server is distinguished by the port that it listens to. Nginx will keep track of every request to the server, which you can write to an access log. The most most important thing though is to tell the server where to find the raw files, which we do in the location context. Now when a user navigates to our domain, it knows where to find the HTML on the file system. And we might want to set up a second location to match any image pattern to the image's directory. Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server. When I replace root with proxy pass, I can point to a completely different server on the Internet. What we've created is a reverse proxy that can handle caching, anonymity, and load balancing. This has been NGINX in 100 seconds. Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.
Nginx.
nginx
It's
it's
like
like
a
a
gateway
gateway
that
that
stands
stands
between
between
the
the
Internet
internet
and
and
your
your
back
back
end
end
infrastructure.
infrastructure
When
when
you
you
visit
visit
a
a
web
web
app,
app
the
the
first
first
place
place
your
your
request
request
will
will
go
go
is
is
to
to
a
a
web
web
server.
server
Its
its
job
job
is
is
to
to
look
look
at
at
the
the
requested
requested
resource
resource
and
and
determine
determine
where
where
to
to
find
find
it
it
on
on
the
the
server,
server
then
then
send
send
it
it
back
back
as
as
the
the
response.
response
In
in
fact,
fact
if
if
you
you
open
open
up
up
the
the
network
network
tab
tab
in
in
Chrome
chrome
app
app
tools
tools
right
right
now.
now
You
you
can
can
look
look
at
at
the
the
server
server
header
header
on
on
any
any
response,
response
and
and
there's
there's
a
a
good
good
chance
chance
it'll
it'll
be
be
Nginx.
nginx
It's
it's
extremely
extremely
popular
popular
with
with
high
high
traffic
traffic
sites
sites
because
because
it
it
can
can
handle
handle
more
more
than
than
10,000
10,000
simultaneous
simultaneous
connections
connections
with
with
its
its
event
event
driven
driven
architecture.
architecture
It's
it's
also
also
commonly
commonly
used
used
as
as
a
a
reverse
reverse
proxy
proxy
where
where
it
it
acts
acts
as
as
a
a
traffic
traffic
light
light
to
to
distribute
distribute
the
the
load
load
to
to
multiple
multiple
back
back
end
end
servers,
servers
while
while
also
also
providing
providing
security
security
and
and
caching
caching
for
for
better
better
performance.
performance
In
in
most
most
cases,
cases
it'll
it'll
be
be
installed
installed
on
on
a
a
Linux
linux
server
server
with
with
the
the
configuration
configuration
file
file
being
being
found
found
in
in
the
the
etc
etc
directory.
directory
You
you
customize
customize
the
the
behavior
behavior
of
of
your
your
server
server
by
by
defining
defining
directives.
directives
A
a
directive
directive
is
is
just
just
a
a
key
key
value
value
pair
pair
or
or
if
if
followed
followed
by
by
braces,
braces
it's
it's
known
known
as
as
a
a
context,
context
which
which
itself
itself
holds
holds
more
more
directives.
directives
In
in
the
the
global
global
context.
context
We
we
might
might
wanna
wanna
specify
specify
things
things
like
like
your
your
username
username
and
and
where
where
to
to
save
save
our
our
error
error
logs.
logs
But
but
most
most
of
of
your
your
configuration
configuration
will
will
likely
likely
be
be
done
done
in
in
the
the
HTTP
http
context.
context
Now
now
one
one
of
of
the
the
most
most
important
important
roles
roles
of
of
NGINX
nginx
is
is
to
to
serve
serve
out
out
static
static
content,
content
like
like
images
images
and
and
HTML.
html
We
we
can
can
handle
handle
that
that
in
in
the
the
HTTP
http
context,
context
next,
next
where
where
we'll
we'll
define
define
1
1
or
or
more
more
servers.
servers
Each
each
server
server
is
is
distinguished
distinguished
by
by
the
the
port
port
that
that
it
it
listens
listens
to.
to
Nginx
nginx
will
will
keep
keep
track
track
of
of
every
every
request
request
to
to
the
the
server,
server
which
which
you
you
can
can
write
write
to
to
an
an
access
access
log.
log
The
the
most
most
most
most
important
important
thing
thing
though
though
is
is
to
to
tell
tell
the
the
server
server
where
where
to
to
find
find
the
the
raw
raw
files,
files
which
which
we
we
do
do
in
in
the
the
location
location
context.
context
Now
now
when
when
a
a
user
user
navigates
navigates
to
to
our
our
domain,
domain
it
it
knows
knows
where
where
to
to
find
find
the
the
HTML
html
on
on
the
the
file
file
system.
system
And
and
we
we
might
might
want
want
to
to
set
set
up
up
a
a
second
second
location
location
to
to
match
match
any
any
image
image
pattern
pattern
to
to
the
the
image's
image's
directory.
directory
Other
other
common
common
things
things
you
you
might
might
handle
handle
in
in
your
your
server
server
config
config
include
include
SSL
ssl
certificates,
certificates
rewrites,
rewrites
and
and
routing
routing
to
to
a
a
proxy
proxy
server.
server
When
when
I
i
replace
replace
root
root
with
with
proxy
proxy
pass,
pass
I
i
can
can
point
point
to
to
a
a
completely
completely
different
different
server
server
on
on
the
the
Internet.
internet
What
what
we've
we've
created
created
is
is
a
a
reverse
reverse
proxy
proxy
that
that
can
can
handle
handle
caching,
caching
anonymity,
anonymity
and
and
load
load
balancing.
balancing
This
this
has
has
been
been
NGINX
nginx
in
in
100
100
seconds.
seconds
Hit
hit
the
the
like
like
button
button
if
if
you
you
wanna
wanna
see
see
more
more
short
short
videos
videos
says,
says
thanks
thanks
for
for
watching,
watching
and
and
I
i
will
will
see
see
you
you
in
in
the
the
next
next
one.
one
success
The speaker explains that Nginx is a gateway used between the Internet and the server infrastructure. It is popular and can handle more than 10,000 simultaneous connections, being used as a reverse proxy for more than 10,000 simultaneous connections. It is also useful for handling traffic and security, and can be customized with Linux tools. It is important to note that it is a multi-year project and will be updated in the future.
NGINX Explained in 100 Seconds
Nginx. It's like a gateway that stands between the Internet and your back end infrastructure. When you visit a web app, the first place your request will go is to a web server. Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response. In fact, if you open up the network tab in Chrome app tools right now. You can look at the server header on any response, and there's a good chance it'll be Nginx. It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture. It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance. In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory. You customize the behavior of your server by defining directives. A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives. In the global context. We might wanna specify things like your username and where to save our error logs. But most of your configuration will likely be done in the HTTP context. Now one of the most important roles of NGINX is to serve out static content, like images and HTML. We can handle that in the HTTP context, next, where we'll define 1 or more servers. Each server is distinguished by the port that it listens to. Nginx will keep track of every request to the server, which you can write to an access log. The most most important thing though is to tell the server where to find the raw files, which we do in the location context. Now when a user navigates to our domain, it knows where to find the HTML on the file system. And we might want to set up a second location to match any image pattern to the image's directory. Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server. When I replace root with proxy pass, I can point to a completely different server on the Internet. What we've created is a reverse proxy that can handle caching, anonymity, and load balancing. This has been NGINX in 100 seconds. Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.
The speaker explains that Nginx is a gateway used between the Internet and the server infrastructure. It is popular and can handle more than 10,000 simultaneous connections, being used as a reverse proxy for more than 10,000 simultaneous connections. It is also useful for handling traffic and security, and can be customized with Linux tools. It is important to note that it is a multi-year project and will be updated in the future.

        [INST]
        You are youtuber called Fireship you make engaging high-intensity and entertaining coding tutorials and tech news. 
        you covers a wide range of topics relevant to programmers, aiming to help them learn and improve their skills quickly.
        
        Given the title of the video : NGINX Explained in 100 Seconds 
        and a small summary : The speaker explains that Nginx is a gateway used between the Internet and the server infrastructure. It is popular and can handle more than 10,000 simultaneous connections, being used as a reverse proxy for more than 10,000 simultaneous connections. It is also useful for handling traffic and security, and can be customized with Linux tools. It is important to note that it is a multi-year project and will be updated in the future.
        [/INST]
        
        Generate the video : Nginx. It's like a gateway that stands between the Internet and your back end infrastructure. When you visit a web app, the first place your request will go is to a web server. Its job is to look at the requested resource and determine where to find it on the server, then send it back as the response. In fact, if you open up the network tab in Chrome app tools right now. You can look at the server header on any response, and there's a good chance it'll be Nginx. It's extremely popular with high traffic sites because it can handle more than 10,000 simultaneous connections with its event driven architecture. It's also commonly used as a reverse proxy where it acts as a traffic light to distribute the load to multiple back end servers, while also providing security and caching for better performance. In most cases, it'll be installed on a Linux server with the configuration file being found in the etc directory. You customize the behavior of your server by defining directives. A directive is just a key value pair or if followed by braces, it's known as a context, which itself holds more directives. In the global context. We might wanna specify things like your username and where to save our error logs. But most of your configuration will likely be done in the HTTP context. Now one of the most important roles of NGINX is to serve out static content, like images and HTML. We can handle that in the HTTP context, next, where we'll define 1 or more servers. Each server is distinguished by the port that it listens to. Nginx will keep track of every request to the server, which you can write to an access log. The most most important thing though is to tell the server where to find the raw files, which we do in the location context. Now when a user navigates to our domain, it knows where to find the HTML on the file system. And we might want to set up a second location to match any image pattern to the image's directory. Other common things you might handle in your server config include SSL certificates, rewrites, and routing to a proxy server. When I replace root with proxy pass, I can point to a completely different server on the Internet. What we've created is a reverse proxy that can handle caching, anonymity, and load balancing. This has been NGINX in 100 seconds. Hit the like button if you wanna see more short videos says, thanks for watching, and I will see you in the next one.
        