#eacceleratro

New Post has been published on http://mocco.sk/running-processwire-on-nginx-lemp-on-debian-wheezyubuntu-13-04/

Running ProcessWire On Nginx (LEMP) On Debian Wheezy/Ubuntu 13.04

Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> Follow me on Twitter Last edited 08/19/2013

This tutorial shows how you can install and run ProcessWire on a Debian Wheezy or Ubuntu 13.04 system that has nginx installed instead of Apache (LEMP = Linux + nginx (pronounced “engine x”) + MySQL + PHP). nginx is a HTTP server that uses much less resources than Apache and delivers pages a lot of faster, especially static files.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

I want to install ProcessWire in a vhost called www.example.com/example.com here with the document root /var/www/www.example.com/web.

You should have a working LEMP installation, as shown in this tutorial:

A note for Ubuntu users:

Because we must run all the steps from this tutorial with root privileges, we can either prepend all commands in this tutorial with the string sudo, or we become root right now by typing

sudo su

2 Installing APC

APC is a free and open PHP opcode cacher for caching and optimizing PHP intermediate code. It’s similar to other PHP opcode cachers, such as eAccelerator and XCache. It is strongly recommended to have one of these installed to speed up your PHP page.

APC can be installed as follows:

apt-get install php-apc

Reload PHP-FPM as follows:

/etc/init.d/php5-fpm reload

3 Installing ProcessWire

The document root of my www.example.com web site is /var/www/www.example.com/web – if it doesn’t exist, create it as follows:

mkdir -p /var/www/www.example.com/web

Next download ProcessWire from the ProcessWire web site, uncompress it and place it in your document root:

mkdir /tmp/processwire cd /tmp/processwire wget https://github.com/ryancramerdesign/ProcessWire/archive/master.zip unzip master.zip rm -f master.zip cd ProcessWire-master mv * /var/www/www.example.com/web/

It is recommended to make the document root and the ProcessWire files in it writable by the nginx daemon which is running as user www-data and group www-data:

chown -R www-data:www-data /var/www/www.example.com/web

If you haven’t already created a MySQL database for processwire (including a MySQL ProcessWire user), you can do that as follows (I name the database pw in this example, and the user is called pw_admin, and his password is pw_admin_password):

mysqladmin -u root -p create pw

mysql -u root -p

GRANT ALL PRIVILEGES ON pw.* TO ‘pw_admin’@'localhost’ IDENTIFIED BY ‘pw_admin_password’; GRANT ALL PRIVILEGES ON pw.* TO ‘pw_admin’@'localhost.localdomain’ IDENTIFIED BY ‘pw_admin_password’;

FLUSH PRIVILEGES;

quit;

Next we create an nginx vhost configuration for our www.example.com vhost in the /etc/nginx/sites-available/ directory as follows:

vi /etc/nginx/sites-available/www.example.com.vhost

server { listen 80; server_name www.example.com example.com; root /var/www/www.example.com/web; if ($http_host != "www.example.com") { rewrite ^ http://www.example.com$request_uri permanent; } index index.php index.html; location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { allow all; log_not_found off; access_log off; } # Deny all attempts to access hidden files such as .htaccess, .htpasswd, .DS_Store (Mac). location ~ /\. { deny all; access_log off; log_not_found off; } client_max_body_size 100M; location ~ /(COPYRIGHT|LICENSE|README|htaccess)\.txt { deny all; } location ~ ^/site(-[^/]+)?/assets/(.*\.php|backups|cache|config|install|logs|sessions) { deny all; } location ~ ^/site(-[^/]+)?/install { deny all; } location ~ ^/(site(-[^/]+)?|wire)/(config(-dev)?|index\.config)\.php { deny all; } location ~ ^/((site(-[^/]+)?|wire)/modules|wire/core)/.*\.(inc|module|php|tpl) { deny all; } location ~ ^/(site(-[^/]+)?|wire)/templates(-admin)?/.*\.(inc|html?|php|tpl) { deny all; } ### GLOBAL REWRITE location / { try_files $uri $uri/ /index.php?it=$uri&$args; } location ~ \.php$ { try_files $uri =404; include /etc/nginx/fastcgi_params; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_intercept_errors on; } }

To enable the vhost, we create a symlink to it from the /etc/nginx/sites-enabled/ directory:

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

Reload nginx for the changes to take effect:

/etc/init.d/nginx reload

Now we can launch the web-based ProcessWire installer by going to http://www.example.com – click on Get Started:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

The installer checks if all prerequisites are fulfilled. When you scroll down…

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

… you will see a warning regarding Apache mod_rewrite. Since we are not using Apache, you can ignore this warning and click on Continue to Next Step:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

In the next step, fill in the MySQL database details, …

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

… then scroll down and click on Continue (the default directory and file permissions are ok):

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

On the next page, fill in a username, password, and email address for the ProcessWire administrator. The default admin login URL should be ok. Click on Create Account afterwards:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

After successful installation, you should see the following screen:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Now write-protect the configuration file and delete the installer:

cd /var/www/www.example.com/web chmod 444 site/config.php rm -f install.php rm -fr site/install/

You can now browse the ProcessWire example site by going to http://www.example.com:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

The backend can be accessed under http://www.example.com/processwire (unless you have specified another admin login URL during installation):

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

This is how the backend looks:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

4 Links

About The Author

Falko Timme is the owner of Timme Hosting (ultra-fast nginx web hosting). He is the lead maintainer of HowtoForge (since 2005) and one of the core developers of ISPConfig (since 2000). He has also contributed to the O’Reilly book “Linux System Administration”.