<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nginx on Dave Hall Consulting</title><link>https://www.davehall.com.au/tags/nginx/</link><description>Recent content in Nginx on Dave Hall Consulting</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Fri, 16 Oct 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.davehall.com.au/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>Making it Easier to Spawn php-cgi on Debian and Ubuntu</title><link>https://www.davehall.com.au/blog/2010/03/16/making-it-easier-spawn-php-cgi-debian-and-ubuntu/</link><pubDate>Tue, 16 Mar 2010 00:00:00 +0000</pubDate><guid>https://www.davehall.com.au/blog/2010/03/16/making-it-easier-spawn-php-cgi-debian-and-ubuntu/</guid><description>Apache is a great web server, but sometimes I need something a bit more lightweight. I already have a bunch of sites using lighttpd, but I&amp;rsquo;m planning on switching them to nginx. Both nginx and lighttpd use FastCGI for running PHP. Getting FastCGI up and running on Ubuntu (or Debian) involves a bit of manual work which can slow down deployment.
The normal process to get nginx and php-cgi up and running is to install the spawn-fcgi package, create a shell script such as /usr/local/bin/php-fastcgi to launch it, then a custom init script, after making both of these executable you need to run update-rc.</description></item><item><title>Howto Setup a Private Package Repository with reprepro and nginx</title><link>https://www.davehall.com.au/blog/2010/02/06/howto-setup-private-package-repository-reprepro-nginx/</link><pubDate>Sat, 06 Feb 2010 00:00:00 +0000</pubDate><guid>https://www.davehall.com.au/blog/2010/02/06/howto-setup-private-package-repository-reprepro-nginx/</guid><description>As the number of servers I am responsible for grows, I have been trying to eliminate all non packaged software in production. Although ubuntu and Debian have massive software repositories, there are some things which just aren&amp;rsquo;t available yet or are internal meta packages. Once the packages are built they need to be deployed to servers. The simplest way to do this is to run a private apt repository. There are a few options for building an apt repository, but the most popular and simplest seems to be reprepro.</description></item></channel></rss>