How to serve multiple domains
Most people serve more than one domain on their Slice(s).
Whether for different domain names or different subdomains of the same domain, the procedure is the same.
Ubuntu Hardy - Apache, Rails and mongrels
Following from the mongrel and mongrel cluster article, we can now look at creating and configuring Apache to proxy to a mongrel cluster so we can serve our Ruby on Rails application.
Ubuntu Hardy - Apache, Rails and thin
Following from the thin web server for Ruby article, let's look at creating and configuring Apache to proxy to thin so we can serve our Ruby on Rails application.
Ubuntu Hardy - using mod_rails to serve your application
Following from the first article, we now have passenger (mod_rails) installed.
As such, we can move on and create a Ruby on Rails application and see how easy it is to serve using passenger.
Ubuntu Hardy - mod_rails installation
Phusion's Passenger (mod_rails) is an exciting development in serving your Ruby on Rails application with the Apache web server.
Incredibly simple to install and use, you can have a rails application up and running in no time. You don't have to worry about ports or setting up a proxy to another server.
Ubuntu Hardy - Apache Virtual Hosts #2
Following on from the first Ubuntu Hardy - Apache Virtual Hosts article, we can now look in detail at some of the settings available to us in the Virtual Hosts file.
This will enable us to have complete control of the domain we want to serve.
Ubuntu Hardy - Apache Virtual Hosts #1
Now we have Apache installed and running, we can configure it to serve multiple domains using Virtual Hosts.
Do note the layout used in these articles is explained here - feel free to use the directories of your choice.
Ubuntu Hardy - Apache configuration #2
Continuing from the first Ubuntu Hardy Apache configuration article, we'll now look at some of the other settings in the main apache2.conf file and what they can do.
Concentrating on efficiency and security, this will end our apache2.conf journey (for now).
Ubuntu Hardy - Apache configuration #1
As we know, Ubuntu Hardy uses a different layout from other non-Debian based systems - let's move on and take a look at the main apache2.conf and ports.conf.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do
Ubuntu Hardy - Apache config layout
Ubuntu Hardy Heron uses a different Apache layout than you may have encountered if you have used Apache with non-Debian based Operating Systems.
The differences are not huge and, indeed, help in configuring and deploying websites.
Ubuntu Hardy - installing Apache and PHP5
Ubuntu Hardy Heron comes with Apache v.2.2.8 and PHP v.5.2.4 and they are easily installed via the default Ubuntu Package Manager 'aptitude'.
The advantage of using aptitude is that you will get any security updates from Ubuntu (if and when distributed) and dependencies are automatically taken care of.
CentOS - Apache configuration #2
Continuing from the first CentOS Apache configuration article, we now look at some of the other settings in the main httpd.conf file and what they can do.
Concentrating on efficiency and security, this will end our httpd.conf journey (for now).
CentOS - Apache configuration #1
Let's take a look at the main httpd.conf for our CentOS Apache install.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do
CentOS - installing Apache and PHP5
CentOS comes with Apache v.2.2.3 and PHP v.5.1.6 and they are easily installed via the default CentOS Package Manager 'yum'.
The advantage of using yum (as opposed to installing via source code) is that you will get any security updates (if and when distributed) and dependencies are automatically taken care of.
Ubuntu Gutsy - mongrel clusters and surviving a reboot
Proxying requests to a mongrel cluster is one of the ways of serving your Ruby on Rails web application.
Let's create a cluster of mongrels and configuring it to restart after a reboot.
Ubuntu Gutsy - Apache vhosts, rails and mongrels
There are several ways of serving a Ruby on Rails application, one of which is to use Apache to proxy requests to mongrels.
There are a few ways of completing this and we're going to look at one simple solution. Other ways will be looked at in future articles.
Ubuntu Gutsy - Apache, SSL and vhosts
So you have a new SSL certificate (see here for self signed certs) and you want to configure Apache to serve your site on the standard HTTPS port (443).
No problem, it's easily done with a new Apache vhosts configuration file.
Ubuntu Gutsy - Apache Virtual Hosts #2
The previous Ubuntu Gutsy Apache Virtual Hosts article introduced the basics of the setting up virtual hosts.
This allowed us to serve multiple domains from a single IP address and Slice. Now we can look in detail at the settings available to us in the Virtual Hosts files and introduce some new ones.
Ubuntu Gutsy - Apache Virtual Hosts
Now we have Apache installed and running, we can configure it to serve multiple domains using Virtual Hosts.
Do note the layout used in these articles is explained here - feel free to use the directories of your choice.
Ubuntu Gutsy - Apache configuration #2
Continuing from the first Ubuntu Gutsy Apache configuration article, we now look at some of the other settings in the main apache2.conf file and what they can do.
Concentrating on efficiency and security, this will end our apache2.conf journey (for now).
Ubuntu Gutsy - Apache configuration #1
Let's take a look at the main apache2.conf and ports.conf for our Ubuntu Gutsy install.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do
Ubuntu Gutsy - Apache config layout
Ubuntu Gutsy uses a slightly different Apache layout than you may have encountered if you have used Apache with non Debian based Operating Systems.
The differences are not huge and, indeed, help in configuring and deploying websites.
Ubuntu Gutsy - installing Apache and PHP5
Ubuntu Gutsy comes with Apache v.2.2.4 and PHP v.5.2.3 and they are easily installed via the default Ubuntu Package Manager 'aptitude'.
The advantage of using aptitude is that you will get any security updates from Ubuntu (if and when distributed) and dependencies are automatically taken care of.
Ubuntu LTS - Apache, SSL and vhosts
Secure connections to your website are vital when entering passwords or entering administration areas.
This article will take you through creating a self-signed certificate and configuring your virtual host to use https (port 443) connections.
Ubuntu LTS - Apache Virtual Hosts #2
The previous Ubuntu LTS Apache Virtual Hosts article introduced the basics of the setting up virtual hosts.
This allowed us to serve multiple domains from a single IP address and Slice. Now we can look in detail at the settings available to us in the Virtual Hosts files and introduce some new ones.
Ubuntu LTS - Apache Virtual Hosts
Now we have Apache installed and running, we can configure it to serve multiple domains using Virtual Hosts.
Do note the layout used in these articles is explained here - feel free to use the directories of your choice.
Ubuntu LTS - Apache configuration #2
Continuing from the first LTS Apache configuration article, we now look at some of the other settings in the main apache2.conf file and what they can do.
Concentrating on efficiency and security, this will end our apache2.conf journey (for now).
Ubuntu LTS - Apache configuration #1
Let's take a look at the main apache2.conf and ports.conf for our LTS (Dapper) install.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do.
Ubuntu LTS - Apache config layout
Ubuntu LTS (Dapper) uses a Debian based Apache layout which differs from the 'classic' layout you may have encountered from other distributions.
The differences are not huge and, indeed, help in configuring and deploying websites.
Ubuntu LTS - installing Apache and PHP5
Ubuntu LTS (Dapper) comes with Apache v.2.0.55 and PHP v.5.1.2. and is easily installed via the 'apt-get' command.
The advantage of using packages is that you will get any security updates from Ubuntu (if and when distributed) and dependencies are automatically taken care of.
Ubuntu Feisty - mongrel clusters and surviving a reboot
Proxying requests to a mongrel cluster is one of the ways of serving your Ruby on Rails web application.
Let's create a cluster of mongrels and configuring it to survive and restart after a reboot.
Ubuntu Feisty - Apache vhosts, rails and mongrels
There are several ways of serving a Ruby on Rails application, one of which is to use Apache to proxy requests to mongrels.
There are a few ways of completing this and we're going to look at one simple solution. Other ways will be looked at in future articles.
Ubuntu Feisty - Apache, SSL and vhosts
Secure connections to your website are vital when entering passwords or entering administration areas.
This article will take you through creating a self-signed certificate and configuring your virtual host to use https (port 443) connections.
Ubuntu Feisty - Apache Virtual Hosts #2
The previous Ubuntu Feisty Apache Virtual Hosts article introduced the basics of the setting up virtual hosts.
This allowed us to serve multiple domains from a single IP address and Slice. Now we can look in detail at the settings available to us in the Virtual Hosts files and introduce some new ones.
Ubuntu Feisty - Apache Virtual Hosts
Now we have Apache installed and running, we can configure it to serve multiple domains using Virtual Hosts.
Do note the layout used in these articles is explained here - feel free to use the directories of your choice.
Ubuntu Feisty - Apache configuration #2
Continuing from the first Feisty Apache configuration article, we now look at some of the other settings in the main apache2.conf file and what they can do.
Concentrating on efficiency and security, this will end our apache2.conf journey (for now).
Ubuntu Feisty - Apache configuration #1
Let's take a look at the main apache2.conf and ports.conf for our Feisty install.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do.
Ubuntu Feisty - Apache config layout
Ubuntu Feisty uses a slightly different Apache layout than you may have encountered if you have used Apache with non Debian based Operating Systems.
The differences are not huge and, indeed, help in configuring and deploying websites.
Ubuntu Feisty - installing Apache and PHP5
Ubuntu Feisty comes with Apache v.2.2.3 and PHP v.5.2.1. and is easily installed via the 'aptitude' command.
The advantage of using packages is that you will get any security updates from Ubuntu (if and when distributed) and dependencies are automatically taken care of.
Debian Etch - mongrel clusters and surviving a reboot
Proxying requests to a mongrel cluster is one of the ways of serving your Ruby on Rails web application with Debian Etch.
Let's look at creating a cluster and configuring it to survive and restart after a reboot.
Debian Etch - Apache Vhosts, rails and mongrels
One of the ways of serving a Ruby on Rails application is to use Apache to proxy requests to mongrels.
There are a few ways of completing this and we're going to look at one simple solution. Other ways will be looked at in future articles.
Debian Etch - Apache, SSL and vhosts
Securing connections to your website are vital when entering passwords or entering administration areas.
This article will take you through creating a self-signed certificate and configuring your virtual host to use https (port 443) connections.
Debian Etch - Apache Virtual Hosts #2
The previous Debian Apache Virtual Hosts article introduced the basics of the setting up virtual hosts.
This enabled us to serve multiple websites from a single IP address and Slice. Let's look at some of the settings available to us in the Virtual Hosts files and introduce some new ones.
Apache Virtual Hosts - permissions
One thing that can cause concern and configuration headaches is virtual hosts permissions.
Using the multiple hosts layout in this article is a good way of keeping your domains in one place and with easy access. Let's take a look at the permissions of the folders.
Debian Etch - Apache Virtual Hosts
Now we have Apache installed and running, let's configure it to serve two different domains using Virtual Hosts.
Do note the layout used in these articles is explained here - feel free to use the directories of your choice.
Debian Etch - Apache configuration #2
Continuing from the first Apache configuration article, we'll now look at some of the other settings in the main apache2.conf file and what they can do.
Concentrating on efficiency and security, this will end our apache2.conf journey (for now).
Debian Etch - Apache configuration #1
Let's take a look at the main apache2.conf and ports.conf for our Debian install.
We're not actually going to change a lot at this point, just look at the main settings and see what they mean and what a change will actually do.
Debian Etch - Apache config layout
Installation of Apache on Debian is relatively easy. Where some confusion arises is the layout Debian uses for configuration of Apache (and Apache configuration in general).
However, the Debian layout is not massively different from a 'classic' layout but enough to warrant an introduction.
Debian Etch - installing Apache and PHP5
Debian Etch comes with Apache v.2.2.3 and PHP v.5.2.0. Although neither of these are the absolutely latest packages they do contain the changes that web administrators generally want, such as Apache's mod_proxy module.
The advantage of using packages is that you will get any security updates from Debian (if and when distributed) and dependencies are easily taken care of.