# killall nginx
# /opt/sbin/nginx

# killall nginx
# /opt/sbin/nginx

# /opt/sbin/nginx

# /opt/sbin/nginx

# killall nginx

      # /opt/sbin/nginx

# killall nginx

      # /opt/sbin/nginx

Restart nginx

@@# killall nginx

        # /opt/sbin/nginx@@

Restart nginx

@@# killall nginx

        # /opt/sbin/nginx@@

Add the following lines to /opt/etc/nginx/nginx.conf http server section:

Change /opt/etc/nginx/nginx.conf http server to listen on port 7007 instead of the default 8082

Page Password

Due to spam, lock the page with password being the same as page title, all lower case.

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

Launch nginx

# /opt/sbin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8008/;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/bin/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. nginx English wiki
3. Nginx - Small, But Very Powerful and Efficient Web Server
4. nginx and Rimuhosting

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

Cool site goodluck :) <a href=" http://community.vh1.com/Post/Cheapest-Airline-Tickets/053DF8A01018ADF530008009FB2F7 ">airline discount ticket military</a> zxypa

i'm fine good work <a href=" http://community.vh1.com/Post/Airline-Discount-Ticket-Military/053DF8A01018ADF530008009FB2F4 ">Airline Discount Ticket Military</a> =-D

Very Good Site http://www.freewebtown.com/ticketsmaster/tragedy-tour-tickets.html Dirt Cheap Airline Tickets >:DD http://www.freewebtown.com/ticketsmaster/traffic-ticket-taxation.html cheap international airline tickets =]

Best Site Good Work <a href=" http://community.vh1.com/Post/Real-Time-Flight-Tracking/053DF8A01018ADF530008009FB2F3 ">Dirt Cheap Airline Tickets</a> 094

Best Site Good Work <a href=" http://community.vh1.com/Post/Military-Discount-Airline-Fares/053DF8A01018ADF530008009FB2F1 ">airline tickets for military families</a> 769665

I'm happy very good site <a href=" http://community.vh1.com/Post/Cheap-International-Airline-Tickets/053DF8A01018ADF530008009FB2E8 ">military discount airline fares</a> 122089

 <a href=" http://community.vh1.com/Post/Discounted-Tickets-For-Military/053DF8A01018ADF530008009FB2E2 ">Cheapest Airline Tickets</a>  64326 

good material thanks <a href=" http://community.vh1.com/Post/Airline-Tickets-For-Military-Families/053DF8A01018ADF530008009FB2DA ">cheap international airline tickets</a> 551581

very best job <a href=" http://community.vh1.com/Post/Dirt-Cheap-Airline-Tickets/053DF8A01018ADF530008009FB2D0 ">cheap international airline tickets</a> oqvp

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

Launch nginx

# /opt/sbin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8008/;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/bin/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. nginx English wiki
3. Nginx - Small, But Very Powerful and Efficient Web Server
4. nginx and Rimuhosting

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

Wonderfull great site <a href=" http://community.vh1.com/Post/Super-Cheap-Airplane-Tickets/053DF8A01018ADF530008009FB2BC ">airline discount ticket military</a> 57709

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

Launch nginx

# /opt/sbin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8008/;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/bin/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. nginx English wiki
3. Nginx - Small, But Very Powerful and Efficient Web Server
4. nginx and Rimuhosting

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

Hello good day <a href=" http://forum.xnxx.com/member.php?u=207091 ">xnxx movies</a> %-)))

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

Launch nginx

# /opt/sbin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8008/;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/bin/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. nginx English wiki
3. Nginx - Small, But Very Powerful and Efficient Web Server
4. nginx and Rimuhosting

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

It's serious <a href=" http://www.lastfm.ru/user/Crowelz/journal/2008/08/24/24otra_pussy_tube ">Lolita Tube</a> %- <a href=" http://www.lastfm.ru/user/Crowelz/journal/2008/08/24/24otmh_incest_tube ">Ebony Tube</a> =]] <a href=" http://www.lastfm.ru/user/Crowelz/journal/2008/08/24/24otpl_lolita_tube ">Free Fucktube</a> xzxt

this post is fantastic <a href=" http://www.lastfm.ru/user/Crowelz/journal/2008/08/24/24ot7c_free_ebonytube ">Free Adulttube</a> %

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

Launch nginx

# /opt/sbin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8008/;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/bin/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. nginx English wiki
3. Nginx - Small, But Very Powerful and Efficient Web Server
4. nginx and Rimuhosting

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

r8rkiR sdlfRnd6M2HvO4

Update

In order to be able to run nginx successfull (if you install nginx only) you need also to install:

zlib openssl pcre libstdc++

please use ipkg install zlib (and the name of the other components previously listed)

CIAO

            proxy_pass      http://127.0.0.1:8008/;

1. nginx English wiki

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Change /opt/nginx/conf/nginx.conf http server to listen on port 7007 instead of the default 80

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

            proxy_pass      http://127.0.0.1:8008;

# /opt/sbin/nginx

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

Add the following lines to /opt/nginx/conf/nginx.conf http server section:

# /opt/bin/php-fcgi -b 9009

Let's say we want to test nginx (localhost:7007) in front of cherokee (localhost:8008, an example of http web/app server) and PHP (localhost:9009, an example of fastcgi).

Preparation

Install cherokee and php-fcgi

# ipkg update
# ipkg install cherokee
# ipkg install php-fcgi

• Browse to http://slug:8008 and you should see cherokee serving /opt/share/www/cherokee/ content.

Verify php-fcgi version

# /opt/bin/php-fcgi -v
PHP 5.1.6 (cgi-fcgi) (built: Aug 25 2006 08:50:32)
...

Prepare a simple info.php, with just a single line of "<?php phpinfo(); ?>"

# mkdir -p /opt/share/www/php
# echo "<?php phpinfo(); ?>" > /opt/share/www/phpinfo.php

Install, config & test nginx.

Basic setup

# ipkg install nginx

Change /opt/nginx/conf/nginx.conf http server to listen on 7007 instead of the default 80

Launch nginx

# /opt/bin/nginx

• Browse to http://slug:7007/ and you should see nginx serving /opt/share/www/nginx/ content.

Add cherokee

Add the following lines to /opt/nginx/conf/nginx.conf http server:

        location /cherokee/ {
            proxy_pass      http://127.0.0.1:8081;
            proxy_redirect  default;
        }

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ (== /opt/nginx/html/) content.
• Browse to http://slug:7007/cherokee/ and you should see cherokee serving /opt/share/www/cherokee/ content thru nginx.

Add php-fcgi

Add the following lines to /opt/nginx/conf/nginx.conf http server:

        location ~ \.php$ {
            fastcgi_pass   127.0.0.1:9009;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /opt/share/www/php/$fastcgi_script_name;
            fastcgi_param  QUERY_STRING     $query_string;
            fastcgi_param  REQUEST_METHOD   $request_method;
            fastcgi_param  CONTENT_TYPE     $content_type;
            fastcgi_param  CONTENT_LENGTH   $content_length;
        }

Launching php-fcgi

# /opt/php-fcgi -b 9009

Bounce nginx

# kill -HUP `cat /opt/var/run/nginx.pid`

• Browse to http://slug:7007/ and you should still see nginx serving /opt/share/www/nginx/ content.
• Browse to http://slug:7007/cherokee/ and you should still see /opt/share/www/cherokee/ content.
• Browse to http://slug:7007/info.php and you should now see the PHP info page!

Tighten security

Try to run PHP or app server as non-root, and only pass certain environment variables to PHP. See reference.

References

1. nginx
2. Nginx - Small, But Very Powerful and Efficient Web Server
3. nginx and Rimuhosting

... to add

... to add

References

• nginx
• Nginx - Small, But Very Powerful and Efficient Web Server
• nginx and Rimuhosting

# ipkg update
# ipkg install nginx

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes requests to the corresponding server based on configuration. The advantage of this approach is:

It makes a lot of sense to use nginx on the slug, especially in the following scenarios:

Installation

1. ipkg update
2. ipkg install nginx

Configuration

Testing

... this doc is still work in progress

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

1. If a slug is all you want to use, for dynamicly generated content as well as static content, yet you don't want to use a full web server;

ReverseProxy is a component that sits in front of web server(s) or app server(s), and routes the request to the corresponding server based on specified configuration. The advantage of this approach is:

• Optionally, if the reverse proxy server supports, it can efficiently serve static content and thus let the app server(s) focus on dynamic content.

On nslu2 with optware, pound and nginx are two lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and serve static content.

It makes a lot of sense to use nginx on the slug, in the following two scenarios:

1. If you want to use a slug to the fullest, and some of your content are dynamicly generated on the slug, yet you don't want to use a full web server;
2. If you would like to use a slug as a reverse proxy in front of your other app server(s).

  * With a reverse proxy server, you can mix and match different server technologies and have them co-exist. For example, subsite1 maybe served by PHP, subsite2 by python app, subsite3 by RoR, and subsite34 by tomcat.

On nslu2 with optware, there are pound and nginx as lightweight reverse proxy servers. Pound is strictly a "reverse proxy and load balancer", while nginx can also connect to upstream (backend) PHP server with fastcgi protocol and efficiently serve static content.

ReverseProxy is a component that sits in front of web server(s) or app server(s), this is to add

• Security
  • App server can be behind reverse proxy server and not directly accessible
  • For selective subsite, reverse proxy server can add SSL encryption
• Flexibility
  • With a reverse proxy server, different server technologies can mix and match and co-exists. Subsite1 maybe served by PHP, subsite2 by python django, subsite3 by RoR, and subsite34 by tomcat.
• Scalability with load balancing.
• Optionally serving static content by the reverse proxy server.

Using apache or even lighttpd for reverse proxy seems overkill.

On nslu2 with optware, there are pound and nginx as lightweight reverse proxy servers. Pound is strictly "reverse proxy and load balancer" only, while nginx can also connect to upstream (backend) PHP server with fastcgi and efficiently serve static content.