Linux Tutorials on the topic “apache”
-
Integrating XCache Into PHP5 (Debian Etch & Apache2)
Author: Falko Timme • Tags: apache, debian, php • Comments: 5Integrating XCache Into PHP5 (Debian Etch & Apache2) This guide explains how to integrate XCache into PHP5 on a Debian Etch system (with Apache2). From the XCache project page: "XCache is a fast, stable PHP opcode cacher that has been tested and is now running on production servers under high load." It's similar to other PHP opcode cachers, such as eAccelerator and APC.
-
Integrating XCache Into PHP5 (Mandriva 2008.0 & Apache2)
Author: Falko Timme • Tags: apache, mandriva, php • Comments: 0Integrating XCache Into PHP5 (Mandriva 2008.0 & Apache2) This guide explains how to integrate XCache into PHP5 on a Mandriva 2008.0 system (with Apache2). From the XCache project page: "XCache is a fast, stable PHP opcode cacher that has been tested and is now running on production servers under high load." It's similar to other PHP opcode cachers, such as eAccelerator and APC.
-
Installing mod_geoip for Apache2 On Debian Etch
Author: Falko Timme • Tags: apache, debian • Comments: 2Installing mod_geoip for Apache2 On Debian Etch This guide explains how to set up mod_geoip with Apache2 on a Debian Etch system. mod_geoip looks up the IP address of the client end user. This allows you to redirect or block users based on their country. You can also use this technology for your OpenX (formerly known as OpenAds or phpAdsNew) ad server to allow geo targeting.
-
-
Setting Up A PHP + MySQL Powered BitTorrent Tracker With RivetTracker
Author: firefly2442 • Tags: apache, linux, php • Comments: 1Setting Up A PHP + MySQL Powered BitTorrent Tracker With RivetTracker Efficient file distribution is an important process for many websites online. BitTorrent makes this easier by sharing the uploading and downloading among clients. This alleviates the bandwidth required by the content provider. This tutorial will show you how to install RivetTracker, a PHP and MySQL driven BitTorrent tracker. RivetTracker is a heavily modified version of PHPBTTracker, written by "DeHackEd". It aims to be easy to use and manage.
-
Chrooting Apache2 With mod_chroot On Debian Etch
Author: Falko Timme •
Tags: apache, debian, security •
Comments: 5 Chrooting Apache2 With mod_chroot On Debian Etch This guide explains how to set up mod_chroot with Apache2 on a Debian Etch system. With mod_chroot, you can run Apache2 in a secure chroot environment and make your server less vulnerable to break-in attempts that try to exploit vulnerabilities in Apache2 or your installed web applications.
-
Splitting Apache Logs With vlogger
Author: Falko Timme • Tags: apache • Comments: 1Splitting Apache Logs With vlogger Vlogger is a little tool with which you can write Apache logs broken down by virtual hosts and days. With vlogger, we need to put just one CustomLog directive into our global Apache configuration, and it will write access logs for each virtual host and day. Therefore, you do not have to split Apache's overall access log into access logs for each virtual host each day, and you do not have to configure Apache to write one access log per virtual host (which could make you run out of file descriptors very fast).
-
Set Up Ubuntu-Server 6.06 LTS As A Firewall/Gateway For Your Small Business Environment
Author: tycho • Tags: antivirus, apache, control panels, postfix, ubuntu • Comments: 2Set Up Ubuntu-Server 6.06 LTS As A Firewall/Gateway For Your Small Business Environment This tutorial shows how to set up a Ubuntu 6.06 LTS server ("Dapper Drake") as a firewall and gateway for small/medium networks. The article covers the installation/configuration of services such as Shorewall, NAT, caching nameserver, DHCP server, VPN server, Webmin, Munin, Apache, Squirrelmail, Postfix, Courier IMAP and POP3, SpamAssassin, ClamAV, and many more.
-
How To Set Up A Loadbalanced High-Availability Apache Cluster
Author: Falko Timme • Tags: apache, debian, high-availability • Comments: 22How To Set Up A Loadbalanced High-Availability Apache Cluster This tutorial shows how to set up a two-node Apache web server cluster that provides high-availability. In front of the Apache cluster we create a load balancer that splits up incoming requests between the two Apache nodes. Because we do not want the load balancer to become another "Single Point Of Failure", we must provide high-availability for the load balancer, too. Therefore our load balancer will in fact consist out of two load balancer nodes that monitor each other using heartbeat, and if one load balancer fails, the other takes over silently.
-
Apache: Creating A Session-Aware Loadbalancer Using mod_proxy_balancer (Debian Etch)
Author: Falko Timme • Tags: apache, debian, high-availability • Comments: 3Apache: Creating A Session-Aware Loadbalancer Using mod_proxy_balancer (Debian Etch) Since Apache 2.1, a new module called mod_proxy_balancer is available which lets you turn a system that has Apache installed into a loadbalancer. This loadbalancer retrieves requested pages from two or more backend webservers and delivers them to the user's computer. Users get the impression that they deal with just one server (the loadbalancer) when in fact there are multiple systems behind the loadbalancer that process the users' requests. By using a loadbalancer, you can lower the load average on your webservers. One important feature of mod_proxy_balancer is that it can keep track of sessions which means that a single user always deals with the same backend webserver. Most websites are database-driven nowadays with user logins etc., and you'd get weird results if a user logs in on one backend webserver, and then his next request goes to another backend webserver, meaning he'd get logged out again. You can avoid this by using mod_proxy_balancer's session-awareness.
-
Merging Multiple Apache Access Logs Into One Overall Access Log
Author: Falko Timme • Tags: linux, apache, debian, high-availability • Comments: 3Merging Multiple Apache Access Logs Into One Overall Access Log Let's assume you have a web application that runs of a cluster of Apache nodes. Each node generates its own Apache access log from which you can generate page view statistics with tools such as Webalizer or AWStats. Obviously you do not want to have page view statistics for each Apache node, but overall page view statistics. To achieve this, we must merge the access logs from each node into one overall access log that we can then feed into Webalizer or AWstats. There is a Perl script called logresolvemerge.pl (part of the AWStats package) that can do this for us.
