Go back to fronty page View most popular entries View latest additions Submit tutorials to UnixTutorials.info
UnixTutorials logo

Search results for Apache - Serving up the Web

OpenBSD Apache - Serving up the Web
Post date: April 11, 2006, 18:04 Category: Network Views: 19
Tutorial quote: The Apache Web Server is installed as part of the OpenBSD base system. This guide will help you configure the web server: (Apache 1.3.12 is released with OpenBSD 2.7 and 1.3.9 with OpenBSD 2.6)

To see how configurable the Apache/OpenBSD combination is we also look at allowing administrators to remotely review the server's status, we setup the system so we allow users on our system to have their own personal web-space. Of course, for the security counscious you probably want to turn some of these things off after you get things up and running.
Unix+clones Configuring Apache for Maximum Performance
Post date: February 12, 2006, 04:02 Category: Optimizing Views: 37
Tutorial quote: Apache is an open-source HTTP server implementation. It is the most popular web server on the Internet; the December 2005 Web Server Survey conducted by Netcraft [1] shows that about 70% of the web sites on Internet are using Apache.

Apache server performance can be improved by adding additional hardware resources such as RAM, faster CPU, etc. But most of the time, the same result can be achieved by custom configuration of the server. This article looks into getting maximum performance out of Apache with the existing hardware resources, specifically on Linux systems. Of course, it is assumed that there is enough hardware resources - especially enough RAM that the server isn't swapping frequently. First two sections look into various Compile-Time and Run-Time configuration options. The Run-Time section assumes that Apache is compiled with prefork MPM. HTTP compression and caching is discussed next. Finally, using separate servers for serving static and dynamic contents is covered. Basic knowledge of compiling and configuring Apache and Linux are assumed.
FreeBSD Lightweight Web Serving with thttpd
Post date: November 30, 2005, 19:11 Category: Software Views: 79
Tutorial quote: The Apache HTTP Server is the most popular web server due to its functionality, stability, and maturity. However, this does not make it suitable for all uses: slow machines and embedded systems may have serious problems running it because of its size. Here is where lightweight HTTP servers come into play, as their low-memory footprints deliver decent results without having to swap data back to disk.

Similarly, these small HTTP servers are suitable to serve static content efficiently so as to allow Apache, mod_perl, mod_python, or even servlet containers to handle dynamic requests without tying up memory-hungry children to serve small images. In other words, these applications can serve as a complement to your existing full-featured web server, not as a replacement.

One of these servers is thttpd, a simple, small, portable, fast, and secure HTTP server. Among its features are support for the HTTP/1.1 standard, CGIs, virtual hosts, and IPv6. This article shows how to install and configure this software under NetBSD. I chose NetBSD not only because it is my preferred OS, but also because it has the ability to run on the most disparate old hardware, where thttpd shows its strengths. I had a Macintosh Performa 630 (a 68LC040 chip at 33MHz) running NetBSD/mac68k 2.0 with thttpd on top of it, serving pages to my home network nicely.
Solaris Configuring Apache
Post date: April 13, 2005, 01:04 Category: Network Views: 81
Tutorial quote: Apache can respond to browser requests from machines on your local network (i.e. an "Intranet" Web server) or from the Internet. The installation of the Solaris OS installed and set up most of the necessary Apache files. As a result, if you want to use your system as a Web server you only need to modify one file.
Unix+clones Apache Maintenance Basics
Post date: April 12, 2005, 21:04 Category: Software Views: 40
Tutorial quote: You've downloaded and configured your Apache server and are ready to move on to the next project. Can it really be left to fend for itself in a darkened room?

Yes. To some degree, anyway. With the exception of configuration testing, once Apache is up, you likely need never think about how the Web server is running.

On the other hand, completely ignoring your Apache installation would be foolhardy. Doing some regular checks and maintenance on your Apache installation helps identify any issues usually before they even become issues and helps you stay up date with the latest security and performance patches. This article covers some of the major steps and maintenance tasks that should be regularly undertaken while the Apache system is running.
Debian How To Set Up A Loadbalanced High-Availability Apache Cluster
Post date: April 28, 2006, 02:04 Category: Network Views: 24
Tutorial quote: 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.
Linux Chrooting Apache
Post date: April 12, 2005, 20:04 Category: Security Views: 49
Tutorial quote: The chroot daemon allows you to run a program and have it see a given directory as the root (/) directory. This effectively locks the process into its very own filesystem ("chroot jail") isolated from the real / filesystem. In this article we will look at how to install the Apache Web server in such an environment.
Unix+clones A web server in a shell script
Post date: March 14, 2006, 03:03 Category: Programming Views: 30
Tutorial quote: Suppose you want to experiment a little with web pages and CGI's, but you don't want the hassle of installing the full Apache package. This quick and dirty shell script could just be what you need.

Put simply, a web server is an application that sends local text files over the network to the clients that request them. If you let another program (for example inetd) deal with the network part, the web server could be reduced to a mere cat "$filename" to stdout. Of course, the difficult part would be to extract that filename out of the HTTP request string: nothing that a Bash script cannot easily do!
Unix+clones DNS name serving through NSD
Post date: July 5, 2005, 02:07 Category: Network Views: 80
Tutorial quote: Given the sheer importance of name servers in providing Domain Name System (DNS) resolution -- a process used by every Web-facing application to translate domain names into IP addresses and vice versa -- not many people put much thought into the available software alternatives for pulling off this feat. One compelling application is NSD, an alternative to the widely deployed BIND name server.
Debian Setting up a local web server in Debian Linux
Post date: January 21, 2006, 01:01 Category: Network Views: 41
Tutorial quote: Any web developer, designer, or webmaster can benefit from having a local web server. Even if that developer has no interest in securing and maintaining the server his or her websites live on, a local server can act as a convenient mirror for testing updates, trying new designs, and other general sand-boxing activities.

Web developers whose hosts utilize the popular LAMP platform (Linux + Apache + MySQL + PHP) are frequently hit with a dilemma. Since understanding Linux is not a prerequisite for website administrators, many of them lack the knowledge necessary for setting up a LAMP server from scratch (or at least they may think so). But thanks to the improved package management on Linux distributions like Debian, installing a functional web server is not nearly the chore it was just a couple years ago.