View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us

Nginx and Perl-FastCGI on Arch Linux

Updated Originally authored by Linode
Select distribution:
Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Deprecated

This guide has been deprecated and is no longer being maintained.

The nginx web server is a fast, lightweight server designed to efficiently handle the needs of both low and high traffic websites. Although commonly used to serve static content, it capable of handling dynamically generated content. The process described in this document centers on the deployment of a FastCGI wrapper for CGI. This makes it possible to deploy all dynamic content that communicates using the CGI protocol. Typically this kind of script is written in Perl, but other CGI scripts will be compatible with this solution.

Set the Hostname

Before you begin installing and configuring the components described in this guide, please make sure you’ve followed our instructions for setting your hostname. Issue the following commands to make sure it is set properly:

hostname
hostname -f

The first command should show your short hostname, and the second should show your fully qualified domain name (FQDN).

Install Required Packages

Issue the following command to install the required packages from the Arch Linux repositories:

pacman -Sy
pacman -S pacman
pacman -S nginx fcgi fcgiwrap spawn-fcgi

Edit the /etc/rc.conf file, adding “nginx” and “fcgiwrap” to the “DEAMONS=” line as shown in the following excerpt:

File: /etc/rc.conf
1

DAEMONS=(syslog-ng network netfs crond sshd ntpd nginx fcgiwrap)

Configure the FastCGI Wrapper

Now, edit the /etc/conf.d/fcgiwrap file to resemble the following example:

File: /etc/conf.d/fcgiwrap
1
2
3
4
5
6
7

SPAWNER='/usr/bin/spawn-fcgi'
FCGI_ADDRESS='127.0.0.1'
FCGI_PORT='9001'
FCGI_USER='http'
FCGI_GROUP='http'
FCGI_EXTRA_OPTIONS=''
SPAWNER_ARGS="-a $FCGI_ADDRESS -p $FCGI_PORT -u $FCGI_USER -g $FCGI_GROUP $FCGI_EXTRA_OPTIONS -- /usr/sbin/fcgiwrap"

Issue the following command to start the FastCGI wrapper for the first time:

/etc/rc.d/fcgiwrap start

Configure Virtual Hosting

Create directories for your web content and logs by issuing the following commands. Be sure to replace “example.com” with your domain name.

mkdir -p /srv/http/example.com/public_html
mkdir /srv/http/example.com/logs

Issue the following commands to create nginx virtual host directories:

mkdir /etc/nginx/conf/sites-available
mkdir /etc/nginx/conf/sites-enabled

Create a virtual host configuration file for your site. Be sure to replace “example.com” with your domain name in the following example configuration.

File: /etc/nginx/conf/sites-available/www.example.com
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

server {
    listen   80;
    server_name example.com www.example.com;
    access_log /srv/http/example.com/logs/access.log;
    error_log /srv/http/example.com/logs/error.log;

    location / {
        root   /srv/http/example.com/public_html;
        index  index.html index.htm;
    }

    location ~ \.cgi$ {
        gzip off;
        include fastcgi_params;
        fastcgi_pass  127.0.0.1:9001;
        fastcgi_index index.cgi;
        fastcgi_param  SCRIPT_FILENAME  /srv/http/example.com/public_html$fastcgi_script_name;
    }
}

This example assumes that all CGI scripts will end with the characters .cgi. If your scripts have some other extension (e.g. .pl or .plx) modify the example to support that. If you want nginx to use the CGI script as an index page, add index.cgi to the index line of the location / block.

Issue the following commands to enable your new virtual host:

cd /etc/nginx/conf/sites-enabled/
ln -s /etc/nginx/conf/sites-available/www.example.com

Edit the file /etc/nginx/conf/nginx.conf, inserting the line include /etc/nginx/conf/sites-enabled/*; at the start of the http { block, as shown in the following file excerpt:

File: /etc/nginx/conf/nginx.conf
1
2
3

http {

    include /etc/nginx/conf/sites-enabled/*;

Issue the following command to start nginx:

/etc/rc.d/nginx start

Test Perl with FastCGI

Create a file called “test.cgi” in your site’s public_html directory with the following contents:

File: /srv/http/example.com/public\\_html/test.cgi
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

#!/usr/bin/perl

print "Content-type:text/html\n\n";
print <<EndOfHTML;
<html><head><title>Perl Environment Variables</title></head>
<body>
<h1>Perl Environment Variables</h1>
EndOfHTML

foreach $key (sort(keys %ENV)) {
    print "$key = $ENV{$key}<br>\n";
}

print "</body></html>";

Make the script executable by issuing the following command:

chmod a+x /srv/http/example.com/public_html/test.cgi

When you visit http://www.example.com/test.cgi in your browser, your Perl environment variables should be shown. Congratulations, you’ve configured the nginx web server to use Perl with FastCGI for dynamic content!

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

This page was originally published on

web server perl nginx

Your Feedback Is Important

Let us know if this guide was helpful to you.

Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.