Catalyst::Manual::Deployment::nginx::FastCGI - Deploying Catalyst with nginx
-=head nginx
+=head1 nginx
Catalyst runs under nginx via FastCGI in a similar fashion as the lighttpd
-standalone server as described above.
+standalone server.
nginx does not have its own internal FastCGI process manager, so you must run
the FastCGI service separately.
-=head3 Configuration
+=head2 Configuration
To configure nginx, you must configure the FastCGI parameters and also the
socket your FastCGI daemon is listening on. It can be either a TCP socket
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;
-
+
# Adjust the socket for your applications!
fastcgi_pass unix:$docroot/myapp.socket;
}
separate file (usually something like C</etc/nginx/fastcgi_params>) and
simply include that file.
-=head3 Non-root configuration
+=head2 Non-root configuration
If you properly specify the PATH_INFO and SCRIPT_NAME parameters your
application will be accessible at any path. The SCRIPT_NAME variable is the
C<$fastcgi_script_name> would be "/myapp/path/of/the/action". Catalyst will
process this accordingly and setup the application base as expected.
-This behavior is somewhat different than Apache and Lighttpd, but is still
+This behavior is somewhat different from Apache and lighttpd, but is still
functional.
+=head2 SSL
+
+Make sure that nginx passes this to your fastcgi. To ensure this, you need
+the following in your nginx config for the SSL vhost:
+
+ fastcgi_param HTTPS on
+
+=head1 MORE INFO
+
For more information on nginx, visit:
L<http://nginx.net>