In the last version (0.9), TileMill has an additional dedicated process to
serve the tiles. We had to change some bits of our server configuration.

Instead of documenting the new configuration in our internal Wiki,
I prefered to share here a few technical lines (quite rough though).

Using PHP-fpm is a way to push PHP execution outside of Apache, one of the main reasons to use it is freeing memory usage of PHP in the apache processes and allowing usage of a threaded Apache server. In this article we'll explain what this sentence means :-) and will detail installation and configuration of php-fpm for a Drupal project.

Drupal comes with a default set of Rewrite Rules in the .htaccess file given by the project. In this article I'll try to provides some recipes for an enhanced mod-rewrite set.

• getting rid of .htaccess
• forbid usage of direct requests to index.php?q=foo (when clean url is activated)

In some Drupal sites, you want to disallow access to the administration interface at /admin. You can use Apache's mod_rewrite module to achieve this.

I've been struggling for a while with a strange bug that I'd like to share. I had two web applications protected with an apache module called mod-auth-openid, which provides an authentication using openid. Here is the sequence diagram for one authentication :

So On a previous blog entry http://www.makina-corpus.org/blog/use-rewritemap-prevent-proxying-some-s... I presented the base for a rewriteRule settings to serve some targeted plone static files directly from apache and without proxying to Plone. No let's make this solution even better.

Let's say we would like to prevent an application server to serve static content. And let's take a complex example, Plone. Plone is a Zope based application server and is not using a clean url-map for static contents. We'll take plone as an example but it's not the only app which is not handling static files outside general uri-application-mapping.

I've been deploying a new Django application at work with Apache and mod_wsgi (it's now the recommended way, instead of mod_python) but that still painful and slow to serve static content.

If you develop a web application you'll come soon at the moment of building your URLs.

I dont know how much people get to this problem, but one thing is sure: when you have a paranoid sysadmin, you might encounter some surprises with PHP and globals.

The annoying case is here when you restrict PHP to the maximum you can, you can't access to the $_REQUEST superglobal.