[MUSIC]

Previously we've shown you how to run a rail server in production, mode but

that doesn't mean the app is ready for production use yet.

It can only take requests on port 3,000 for one thing,

meaning that ain't URL linking to it would have to specify port 3,000.

It's also exposed directly to the web, meaning that it's easy for

malicious parties to carry out denial of service attacks on it.

That could slow down or disable your site for your actual users.

So in this workshop we're going to show you how to setup a reverse proxy, between

the rails app and the internet at large, the proxy will take requests on port 80

which is the default used by browsers forward them to your Rails app and

then forward the Rails responses back to the browsers that request them.

We're going to use a high performance web server called NGINX or reverse proxy.

NGINX will also serve the static files on our apps public directory so

rails doesn't have to.

Well also set up a unicorn.

An http server that will manage connections to your actual Rails app.

Unicorn sets up multiple worker processes that take turns

handling requests forwarded to them by nginx.

if there's some kind of problem and

a worker takes too long to respond he gets shut down.

And another worker is created to replace it.

Unicorn is good for your site's stability and speed.