Configuring Apache
To keep with my debian-ish standards for how I manage my web server I wanted my new WordPress installation to show up in my /var/www directory using the name of the site it should be accessed at [blog292.my.home]. To accomplish this, I created a soft link to the word press install. Then I created a new Apache config file in /etc/apache2/sites-available for my new site.
sudo ln -s /usr/share/wordpress.2.9.2/ /var/www/blog292.my.home sudo nano /etc/apache2/sites-available/blog292.my.home
The Apache config file ended up looking like this.
<VirtualHost *> RewriteEngine On ServerAdmin admin@my.home ServerName blog292.my.home DocumentRoot /var/www/blog292.my.home <Directory /var/www/blog292.my.home> Options Indexes FollowSymLinks Options Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI Multiviews AllowOverride Options FileInfo AuthConfig Limit <Limit GET POST OPTIONS> Order allow,deny Allow from 192.168.0 </Limit> <LimitExcept GET POST OPTIONS> Order deny,allow Allow from 192.168.0 </LimitExcept> </Directory> ErrorLog /var/log/apache2/blog292.my.home-error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog /var/log/apache2/blog292.my.home-access.log combined ServerSignature On </VirtualHost>
Next I enabled the new site and restarted Apache.
sudo a2ensite blog292.my.home sudo /etc/init.d/apache2 restart
And finally, I updated my local DNS server to alias blog292.my.home to my web server web.my.home.
sudo nano /etc/bind/zones/my.home.db
The entry I added was as follows
blog292 IN CNAME web
Start ‘er up
After a few quick ping checks on the new DNS name, I crossed my fingers and pointed my browser to the WordPress initial install location [http://blog292.my.home/wp-admin/install.php].
The installation came right up, and a few clicks later, my WordPress 2.9.2 sandbox was up and running.
[...] my previous post, I got the latest version of WordPress up and running on one of my home test servers. So what was [...]