#document root

[martink279]

New Post has been published on WebSetNet

New Post has been published on http://websetnet.com/install-cs-cart-v4-on-nginx/

Install CS-Cart v4 on nginx

How to install and run CS-Cart version 4 on NGINX, for the purposes of this how-to we are installing CS-Cart on sitename.com, it assumes you have a working LEMP installation.

Step one: Install CS-Cart

The document root for www.sitename.com will be /var/www/www.sitename.com/public_html – if this folder doesn’t exist you need to create it:

mkdir -p /var/www/www.sitename.com/public_html

Then download CS-Cart version 4 to your computer, upload it into a temporary directory (for example: /tmp/install) then decompress:

cd /tmp/cscart tar xvfz cscart_v4.2.2.tgz rm -f cscart_v4.2.2.tgz mv * .htaccess /var/www/www.sitename.com/public_html/

You need to make the document root and CS-Cart files writable by the nginx daemon:

chown -R www-data:www-data /var/www/www.sitename.com/public_html

Step two: Create database

This step will create a database called cs-cart and a user called cscart_user with password xyz123

mysqladmin -u root -p create cs_cart mysql -u root -p GRANT ALL PRIVILEGES ON cs_cart.* TO 'cscart_user'@'localhost' IDENTIFIED BY 'xyz123'; GRANT ALL PRIVILEGES ON cs_cart.* TO 'cscart_user'@'localhost.localdomain' IDENTIFIED BY 'xyz123'; FLUSH PRIVILEGES; quit;

Step three: nginx config

Stop the nginx service :

$ service nginx stop

Replace the contents from /etc/nginx/nginx.conf with the below:

user www-data; worker_processes 8; error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid; events worker_connections 1024; http include /etc/nginx/mime.types; default_type application/octet-stream; log_format main ‘$ remote_addr – $ remote_user [$ time_local] “$ request” ‘ ‘$ status $ body_bytes_sent “$ http_referer” ‘ ‘”$ http_user_agent” “$ http_x_forwarded_for”‘; access_log /var/log/nginx/access.log main; sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; server_tokens off; gzip on; gzip_vary on; gzip_disable “msie6″; gzip_http_version 1.0; gzip_comp_level 8; gzip_proxied any; gzip_types text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript; client_body_temp_path /tmp/client_temp; # proxy_temp_path /tmp/proxy_temp; # proxy_cache_path /var/cache/nginx/proxy_cache levels=2 keys_zone=nginx:100m inactive=200m max_size=5000m; include /etc/nginx/conf.d/*.conf; fastcgi_cache_path /var/cache/nginx levels=1:2 keys_zone=cache:10m max_size=1000m inactive=60m; fastcgi_cache_key “$ scheme$ request_method$ host$ request_uri”;

Step three: Create vhost config

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

server svg

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

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

test the config by using the following command:

nginx -t

then run

service nginx restart

Step Four : Web Based installer

Now launch the CS-Cart installer by going to http://www.sitename.com and continue with the install as normal

[moccosk]

New Post has been published on Mocco

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”.

Check out the original source here.

[moccosk]

New Post has been published on Mocco

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

Running CS-Cart 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 CS-Cart 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 CS-Cart 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 CS-Cart

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 CS-Cart from the CS-Cart web site (I’m using CS-Cart Ultimate here) to your local computer; from there, upload it to your server (e.g. create a /tmp/cscart directory and upload it there), uncompress it and place it in your document root:

cd /tmp/cscart tar xvfz cscart_v4.0.1-ultimate.tgz rm -f rm -f cscart_v4.0.1-ultimate.tgz mv * .htaccess /var/www/www.example.com/web/

It is recommended to make the document root and the CS-Cart 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 CS-Cart (including a MySQL CS-Cart user), you can do that as follows (I name the database cscart in this example, and the user is called cscart_admin, and his password is cscart_admin_password):

mysqladmin -u root -p create cscart

mysql -u root -p

GRANT ALL PRIVILEGES ON cscart.* TO ‘cscart_admin’@'localhost’ IDENTIFIED BY ‘cscart_admin_password’; GRANT ALL PRIVILEGES ON cscart.* TO ‘cscart_admin’@'localhost.localdomain’ IDENTIFIED BY ‘cscart_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; rewrite /api/(.*)$ /api.php?_d=$1&ajax_custom=1 last; location ~ \.(png|gif|ico|swf|jpe?g|js|css|ttf|svg|eot|woff)$ { if (!-e $request_filename){ rewrite ^/(.*?)\/(.*)$ /$2 last; } expires 1w; } location ~ store_closed.html$ { if (!-e $request_filename){ rewrite ^/(.*?)\/(.*)$ /$2 last; } } location / { index index.php; try_files $uri $uri/ /index.php?sef_rewrite=1&$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; fastcgi_temp_file_write_size 10m; fastcgi_busy_buffers_size 512k; fastcgi_buffer_size 512k; fastcgi_buffers 16 512k; fastcgi_read_timeout 1200; } }

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 CS-Cart installer by going to http://www.example.com/install – accept the license and click on Next step:

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

On the next page, fill in your MySQL database details, then scroll down…

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

… and provide an email address (this will be your username) and password for the CS-Cart backend; you can also choose to install demo data for your CS-Cart shop:

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

On the next page, select the store mode. If you have a CS-Cart license number, select Full, otherwise Free or Trial:

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

If everything goes fine, the installation should finish successfully. It is recommended that you click on the Go to the Settings Wizard button to configure the initial settings for your CS-Cart shop.

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

You can reach the backend under http://www.example.com/admin.php (unless you have chosen to rename the admin.php script in the Settings Wizard):

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

This is how your CS-Cart shop looks if you have chosen to install demo data during installation:

(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”.

Check out the original source here.

[moccosk]

New Post has been published on Mocco

New Post has been published on http://mocco.sk/installing-nginx-with-php5-and-php-fpm-and-mysql-support-lemp-on-ubuntu-13-04/

Installing Nginx With PHP5 (And PHP-FPM) And MySQL Support (LEMP) On Ubuntu 13.04

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

Nginx (pronounced “engine x”) is a free, open-source, high-performance HTTP server. Nginx is known for its stability, rich feature set, simple configuration, and low resource consumption. This tutorial shows how you can install Nginx on an Ubuntu 13.04 server with PHP5 support (through PHP-FPM) and MySQL support (LEMP = Linux + nginx (pronounced “engine x”) + MySQL + PHP) .

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

1 Preliminary Note

In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100. These settings might differ for you, so you have to replace them where appropriate.

I’m running all the steps in this tutorial with root privileges, so make sure you’re logged in as root:

sudo su

2 Installing MySQL 5

In order to install MySQL, we run

apt-get install mysql-server mysql-client

You will be asked to provide a password for the MySQL root user – this password is valid for the user root@localhost as well as [email protected], so we don’t have to specify a MySQL root password manually later on:

New password for the MySQL “root” user: <– yourrootsqlpassword Repeat password for the MySQL “root” user: <– yourrootsqlpassword

3 Installing Nginx

Nginx is available as a package for Ubuntu 13.04 which we can install as follows:

apt-get install nginx

Start nginx afterwards:

/etc/init.d/nginx start

Type in your web server’s IP address or hostname into a browser (e.g. http://192.168.0.100), and you should see the following page:

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

The default nginx document root on Ubuntu 13.04 is /usr/share/nginx/html.

4 Installing PHP5

We can make PHP5 work in nginx through PHP-FPM (PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites) which we install as follows:

apt-get install php5-fpm

PHP-FPM is a daemon process (with the init script /etc/init.d/php5-fpm) that runs a FastCGI server on the socket /var/run/php5-fpm.sock.

5 Configuring nginx

The nginx configuration is in /etc/nginx/nginx.conf which we open now:

vi /etc/nginx/nginx.conf

The configuration is easy to understand (you can learn more about it here: http://wiki.nginx.org/NginxFullExample and here: http://wiki.nginx.org/NginxFullExample2)

First (this is optional) adjust the number of worker processes and set the keepalive_timeout to a reasonable value:

[...] worker_processes 4; [...] keepalive_timeout 2; [...]

The virtual hosts are defined in server {} containers. The default vhost is defined in the file /etc/nginx/sites-available/default – let’s modify it as follows:

vi /etc/nginx/sites-available/default

[...] server { listen 80; listen [::]:80 default_server ipv6only=on; root /usr/share/nginx/html; index index.php index.html index.htm; # Make site accessible from http://localhost/ server_name _; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ /index.html; # Uncomment to enable naxsi on this location # include /etc/nginx/naxsi.rules } location /doc/ { alias /usr/share/doc/; autoindex on; allow 127.0.0.1; allow ::1; deny all; } # Only for nginx-naxsi used with nginx-naxsi-ui : process denied requests #location /RequestDenied { # proxy_pass http://127.0.0.1:8080; #} #error_page 404 /404.html; # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/share/nginx/html; } # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini # With php5-cgi alone: #fastcgi_pass 127.0.0.1:9000; # With php5-fpm: fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # location ~ /\.ht { deny all; } } [...]

Uncomment both listen lines to make nginx listen on port 80 IPv4 and IPv6.

server_name _; makes this a default catchall vhost (of course, you can as well specify a hostname here like www.example.com).

I’ve added index.php to the index line. root /usr/share/nginx/html; means that the document root is the directory /usr/share/nginx/html.

The important part for PHP is the location ~ \.php$ {} stanza. Uncomment it to enable it. Please note that I’ve added the line try_files $uri =404; to prevent zero-day exploits (see http://wiki.nginx.org/Pitfalls#Passing_Uncontrolled_Requests_to_PHP and http://forum.nginx.org/read.php?2,88845,page=3).

Now save the file and reload nginx:

/etc/init.d/nginx reload

Next open /etc/php5/fpm/php.ini…

vi /etc/php5/fpm/php.ini

… and set cgi.fix_pathinfo=0:

[...] ; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI. PHP's ; previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok ; what PATH_INFO is. For more information on PATH_INFO, see the cgi specs. Setting ; this to 1 will cause PHP CGI to fix its paths to conform to the spec. A setting ; of zero causes PHP to behave as before. Default is 1. You should fix your scripts ; to use SCRIPT_FILENAME rather than PATH_TRANSLATED. ; http://php.net/cgi.fix-pathinfo cgi.fix_pathinfo=0 [...]

Reload PHP-FPM:

/etc/init.d/php5-fpm reload

Now create the following PHP file in the document root /usr/share/nginx/html:

vi /usr/share/nginx/html/info.php

Now we call that file in a browser (e.g. http://192.168.0.100/info.php):

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

As you see, PHP5 is working, and it’s working through FPM/FastCGI, as shown in the Server API line. If you scroll further down, you will see all modules that are already enabled in PHP5. MySQL is not listed there which means we don’t have MySQL support in PHP5 yet.

6 Getting MySQL Support In PHP5

To get MySQL support in PHP, we can install the php5-mysql package. It’s a good idea to install some other PHP5 modules as well as you might need them for your applications. You can search for available PHP5 modules like this:

apt-cache search php5

Pick the ones you need and install them like this:

apt-get install php5-mysql php5-curl php5-gd php5-intl php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-ming php5-ps php5-pspell php5-recode php5-snmp php5-sqlite php5-tidy php5-xmlrpc php5-xsl

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

Now reload PHP-FPM:

/etc/init.d/php5-fpm reload

Now reload http://192.168.0.100/info.php in your browser and scroll down to the modules section again. You should now find lots of new modules there, including the MySQL module:

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

7 Making PHP-FPM Use A TCP Connection

By default PHP-FPM is listening on the socket /var/run/php5-fpm.sock. It is also possible to make PHP-FPM use a TCP connection. To do this, open /etc/php5/fpm/pool.d/www.conf…

vi /etc/php5/fpm/pool.d/www.conf

… and make the listen line look as follows:

[...] ;listen = /var/run/php5-fpm.sock listen = 127.0.0.1:9000 [...]

This will make PHP-FPM listen on port 9000 on the IP 127.0.0.1 (localhost). Make sure you use a port that is not in use on your system.

Then reload PHP-FPM:

/etc/init.d/php5-fpm reload

Next go through your nginx configuration and all your vhosts and change the line fastcgi_pass unix:/var/run/php5-fpm.sock; to fastcgi_pass 127.0.0.1:9000;, e.g. like this:

vi /etc/nginx/sites-available/default

[...] location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini # With php5-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php5-fpm: #fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } [...]

Finally reload nginx:

/etc/init.d/nginx reload

8 CGI/Perl Scripts

If you want to serve CGI/Perl scripts with nginx, please read this tutorial: Serving CGI Scripts With Nginx On Debian Squeeze/Ubuntu 11.04

The recommended way is to use fcgiwrap (chapter 4).

9 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”.

Check out the original source here.

[moccosk]

New Post has been published on Mocco

New Post has been published on http://mocco.sk/server-monitoring-with-munin-and-monit-on-debian-wheezy/

Server Monitoring With munin And monit On Debian Wheezy

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

In this article I will describe how you can monitor your Debian Wheezy server with munin and monit. munin produces nifty little graphics about nearly every aspect of your server (load average, memory usage, CPU usage, MySQL throughput, eth0 traffic, etc.) without much configuration, whereas monit checks the availability of services like Apache, MySQL, Postfix and takes the appropriate action such as a restart if it finds a service is not behaving as expected. The combination of the two gives you full monitoring: graphics that lets you recognize current or upcoming problems (like “We need a bigger server soon, our load average is increasing rapidly.”), and a watchdog that ensures the availability of the monitored services.

Although munin lets you monitor more than one server, we will only discuss the monitoring of the system where it is installed here.

This tutorial was written for Debian Wheezy, but the configuration should apply to other distributions with little changes as well.

I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

1 Preliminary Note

Our system’s hostname is server1.example.com, and we have a web site www.example.com on it with the document root /var/www/www.example.com/web.

2 Install And Configure munin

To install munin on Debian Wheezy, we do this:

apt-get install munin munin-node munin-plugins-extra

Enable a few extra munin plugins:

cd /etc/munin/plugins ln -s /usr/share/munin/plugins/mysql_ mysql_ ln -s /usr/share/munin/plugins/mysql_bytes mysql_bytes ln -s /usr/share/munin/plugins/mysql_innodb mysql_innodb ln -s /usr/share/munin/plugins/mysql_isam_space_ mysql_isam_space_ ln -s /usr/share/munin/plugins/mysql_queries mysql_queries ln -s /usr/share/munin/plugins/mysql_slowqueries mysql_slowqueries ln -s /usr/share/munin/plugins/mysql_threads mysql_threads

Next, we must edit the munin configuration file /etc/munin/munin.conf. Uncomment the dbdir, htmldir, logdir, rundir, and tmpldir lines (the default values are fine). We want munin to use the name server1.example.com instead of localhost.localdomain in the HTML output, therefore we replace localhost.localdomain with server1.example.com in the simple host tree section. Without the comments, the changed file looks like this:

vi /etc/munin/munin.conf

# Example configuration file for Munin, generated by 'make build' # The next three variables specifies where the location of the RRD # databases, the HTML output, logs and the lock/pid files. They all # must be writable by the user running munin-cron. They are all # defaulted to the values you see here. # dbdir /var/lib/munin htmldir /var/cache/munin/www logdir /var/log/munin rundir /var/run/munin # Where to look for the HTML templates # tmpldir /etc/munin/templates # Where to look for the static www files # #staticdir /etc/munin/static # temporary cgi files are here. note that it has to be writable by # the cgi user (usually nobody or httpd). # # cgitmpdir /var/lib/munin/cgi-tmp # (Exactly one) directory to include all files from. includedir /etc/munin/munin-conf.d [...] # a simple host tree [server1.example.com] address 127.0.0.1 use_node_name yes [...]

We should find the Apache configuration file for munin /etc/apache2/conf.d/munin (which actually is a symlink to /etc/munin/apache.conf) – it defines an alias called munin to munin’s HTML output directory /var/cache/munin/www which means we can access munin from all web sites on this server by using the relative path /munin (e.g. http://www.example.com/munin).

Make sure you comment out the line Allow from localhost 127.0.0.0/8 ::1 and add Allow from all instead (otherwise you will only be able to access the munin output from localhost):

vi /etc/apache2/conf.d/munin

# Enable this for template generation Alias /munin /var/cache/munin/www # Enable this for cgi-based templates #Alias /munin-cgi/static /var/cache/munin/www/static #ScriptAlias /munin-cgi /usr/lib/munin/cgi/munin-cgi-html #<Location /munin-cgi> # Order allow,deny # Allow from localhost 127.0.0.0/8 ::1 # AuthUserFile /etc/munin/munin-htpasswd # AuthName "Munin" # AuthType Basic # require valid-user #</Location> <Directory /var/cache/munin/www> Order allow,deny #Allow from localhost 127.0.0.0/8 ::1 Allow from all Options None # This file can be used as a .htaccess file, or a part of your apache # config file. # # For the .htaccess file option to work the munin www directory # (/var/cache/munin/www) must have "AllowOverride all" or something # close to that set. # # AuthUserFile /etc/munin/munin-htpasswd # AuthName "Munin" # AuthType Basic # require valid-user # This next part requires mod_expires to be enabled. # # Set the default expiration time for files to 5 minutes 10 seconds from # their creation (modification) time. There are probably new files by # that time. # <IfModule mod_expires.c> ExpiresActive On ExpiresDefault M310 </IfModule> </Directory> [...]

Restart Apache:

/etc/init.d/apache2 restart

Then restart munin:

/etc/init.d/munin-node restart

Now wait a few minutes so that munin can produce its first output, and then go to http://www.example.com/munin/ in your browser, and you see the first statistics. After a few days this could look like this:

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

(This is just a small excerpt of the many graphics that munin produces…)

3 Password-Protect The munin Output Directory (Optional)

Now it is a good idea to password-protect the munin output directory unless you want everybody to be able to see every little statistic about your server.

To do this, we must create the password file /etc/munin/munin-htpasswd. We want to log in with the username admin, so we do this:

htpasswd -c /etc/munin/munin-htpasswd admin

Enter a password for admin. Then open /etc/apache2/conf.d/munin again…

vi /etc/apache2/conf.d/munin

… and uncomment the following section:

[...] AuthUserFile /etc/munin/munin-htpasswd AuthName "Munin" AuthType Basic require valid-user [...]

Then restart Apache:

/etc/init.d/apache2 restart

Server Monitoring With munin And monit On Debian Wheezy – Page 2

Check out the original source here.

[moccosk]

New Post has been published on Mocco

New Post has been published on http://mocco.sk/installing-apache2-with-php5-and-mysql-support-on-debian-wheezy/

Installing Apache2 With PHP5 And MySQL Support On Debian Wheezy

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

LAMP is short for Linux, Apache, MySQL, PHP. This tutorial shows how you can install an Apache2 webserver on a Debian Wheezy server with PHP5 support (mod_php) and MySQL support.

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

1 Preliminary Note

In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100. These settings might differ for you, so you have to replace them where appropriate.

2 Installing MySQL 5

First we install MySQL 5 like this:

apt-get install mysql-server mysql-client

You will be asked to provide a password for the MySQL root user – this password is valid for the user root@localhost as well as [email protected], so we don’t have to specify a MySQL root password manually later on:

New password for the MySQL “root” user: <– yourrootsqlpassword Repeat password for the MySQL “root” user: <– yourrootsqlpassword

3 Installing Apache2

Apache2 is available as a Debian package, therefore we can install it like this:

apt-get install apache2

Now direct your browser to http://192.168.0.100, and you should see the Apache2 placeholder page (It works!):

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

Apache’s default document root is /var/www on Debian, and the configuration file is /etc/apache2/apache2.conf. Additional configurations are stored in subdirectories of the /etc/apache2 directory such as /etc/apache2/mods-enabled (for Apache modules), /etc/apache2/sites-enabled (for virtual hosts), and /etc/apache2/conf.d.

4 Installing PHP5

We can install PHP5 and the Apache PHP5 module as follows:

apt-get install php5 libapache2-mod-php5

We must restart Apache afterwards:

/etc/init.d/apache2 restart

5 Testing PHP5 / Getting Details About Your PHP5 Installation

The document root of the default web site is /var/www. We will now create a small PHP file (info.php) in that directory and call it in a browser. The file will display lots of useful details about our PHP installation, such as the installed PHP version.

vi /var/www/info.php

Now we call that file in a browser (e.g. http://192.168.0.100/info.php):

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

As you see, PHP5 is working, and it’s working through the Apache 2.0 Handler, as shown in the Server API line. If you scroll further down, you will see all modules that are already enabled in PHP5. MySQL is not listed there which means we don’t have MySQL support in PHP5 yet.

6 Getting MySQL Support In PHP5

To get MySQL support in PHP, we can install the php5-mysql package. It’s a good idea to install some other PHP5 modules as well as you might need them for your applications. You can search for available PHP5 modules like this:

apt-cache search php5

Pick the ones you need and install them like this:

apt-get install php5-mysql php5-curl php5-gd php5-intl php-pear php5-imagick php5-imap php5-mcrypt php5-memcache php5-ming php5-ps php5-pspell php5-recode php5-snmp php5-sqlite php5-tidy php5-xmlrpc php5-xsl

Now restart Apache2:

/etc/init.d/apache2 restart

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

Now restart Apache:

/etc/init.d/apache2 restart

Now reload http://192.168.0.100/info.php in your browser and scroll down to the modules section again. You should now find lots of new modules there, including the MySQL module:

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

7 phpMyAdmin

phpMyAdmin is a web interface through which you can manage your MySQL databases. It’s a good idea to install it:

apt-get install phpmyadmin

You will see the following questions:

Web server to reconfigure automatically: <– apache2 Configure database for phpmyadmin with dbconfig-common? <– No

Afterwards, you can access phpMyAdmin under http://192.168.0.100/phpmyadmin/:

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

8 Links

Check out the original source here.

[moccosk]

New Post has been published on Mocco

New Post has been published on http://mocco.sk/running-prestashop-1-5-x-on-nginx-lemp-on-debian-wheezyubuntu-12-10/

Running PrestaShop 1.5.x On Nginx (LEMP) On Debian Wheezy/Ubuntu 12.10

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

This tutorial shows how you can install and run a PrestaShop 1.5.x web site on a Debian Wheezy or Ubuntu 12.10 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 PrestaShop 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 PrestaShop

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 PrestaShop from http://www.prestashop.com/en/download to your local computer; from there, upload it to your server (e.g. the /tmp directory), unzip it and place it in your document root:

cd /tmp unzip prestashop_1.5.4.0.zip cd prestashop/ mv * /var/www/www.example.com/web/

It is recommended to make the document root and the PrestaShop 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 PrestaShop (including a MySQL PrestaShop user), you can do that as follows (I name the database presta in this example, and the user is called presta_admin, and his password is presta_admin_password):

mysqladmin -u root -p create presta

mysql -u root -p

GRANT ALL PRIVILEGES ON presta.* TO ‘presta_admin’@'localhost’ IDENTIFIED BY ‘presta_admin_password’; GRANT ALL PRIVILEGES ON presta.* TO ‘presta_admin’@'localhost.localdomain’ IDENTIFIED BY ‘presta_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; } rewrite ^/api/?(.*)$ /webservice/dispatcher.php?url=$1 last; rewrite ^/([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$1$2$3.jpg last; rewrite ^/([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$1$2$3$4.jpg last; rewrite ^/([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$1$2$3$4$5.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$4/$1$2$3$4$5$6.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.jpg last; rewrite ^/c/([0-9]+)(\-[\.*_a-zA-Z0-9-]*)(-[0-9]+)?/.+\.jpg$ /img/c/$1$2$3.jpg last; rewrite ^/c/([a-zA-Z_-]+)(-[0-9]+)?/.+\.jpg$ /img/c/$1$2.jpg last; rewrite ^/images_ie/?([^/]+)\.(jpe?g|png|gif)$ /js/jquery/plugins/fancybox/images/$1.$2 last; try_files $uri $uri/ /index.php$is_args$args; error_page 404 /index.php?controller=404; location ~* \.(gif)$ { expires 2592000s; } location ~* \.(jpeg|jpg)$ { expires 2592000s; } location ~* \.(png)$ { expires 2592000s; } location ~* \.(css)$ { expires 604800s; } location ~* \.(js|jsonp)$ { expires 604800s; } location ~* \.(js)$ { expires 604800s; } location ~* \.(ico)$ { expires 31536000s; } 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 PrestaShop installer by going to http://www.example.com/install/ – first you have to select the language you want the installer to use:

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

Next accept the PrestaShop license:

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

Fill in your database details and click on Next:

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

Running PrestaShop 1.5.x On Nginx (LEMP) On Debian Wheezy/Ubuntu 12.10 – Page 2

Check out the original source here.

[moccosk]

New Post has been published on Mocco

New Post has been published on http://mocco.sk/running-activecollab-3-on-nginx-lemp-on-debian-wheezyubuntu-12-10/

Running ActiveCollab 3 On Nginx (LEMP) On Debian Wheezy/Ubuntu 12.10

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

This tutorial shows how you can install and run activeCollab 3 on a Debian Wheezy or Ubuntu 12.10 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 activeCollab 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 activeCollab

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 activeCollab from the activeCollab web site (you need to buy a license – it’s not freeware) to your local computer; from there, upload it to your server (e.g. the /tmp directory), unzip it and place it in your document root:

cd /tmp unzip activecollab-corporate-3.2.12.zip cd for-upload/ mv * /var/www/www.example.com/web/

It is recommended to make the document root and the activeCollab 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 activeCollab (including a MySQL activeCollab user), you can do that as follows (I name the database activecollab in this example, and the user is called ac_admin, and his password is ac_admin_password):

mysqladmin -u root -p create activecollab

mysql -u root -p

GRANT ALL PRIVILEGES ON activecollab.* TO ‘ac_admin’@'localhost’ IDENTIFIED BY ‘ac_admin_password’; GRANT ALL PRIVILEGES ON activecollab.* TO ‘ac_admin’@'localhost.localdomain’ IDENTIFIED BY ‘ac_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; } location / { try_files $uri $uri/ /index.phppath_info=$uri&$args; access_log off; expires max; } 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 activeCollab installer by going to http://www.example.com – click on the Validate button to have the installer check if the system requirements are fulfilled:

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

If the system requirements are fulfilled, you can now fill in your database details and click on Connect:

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

Next, specify an email address and password for the administrator account, accept the license agreement and click on Install:

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

That’s it – click on the Log in Now! button or go to http://www.example.com/public/index.php…

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

… to log into activeCollab:

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

This is how the activeCollab interface 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”.

Check out the original source here.