The layout for Apache will become:

<layout DIYMacServer>
    prefix:        /usr/local/apache2
    exec_prefix:   ${prefix}
    bindir:        ${exec_prefix}/bin
    sbindir:       ${exec_prefix}/bin
    libdir:        ${exec_prefix}/lib
    libexecdir:    ${exec_prefix}/modules
    mandir:        ${prefix}/man
    sysconfdir:    /etc/httpd/
    datadir:       /var/www
    installbuilddir: ${datadir}/build
    errordir:      ${datadir}/error
    iconsdir:      ${datadir}/icons
    htdocsdir:     ${datadir}/htdocs
    manualdir:     ${datadir}/manual
    cgidir:        ${datadir}/cgi-bin
    includedir:    ${prefix}/include
    localstatedir: /var
    runtimedir:    ${localstatedir}/run
    logfiledir:    ${localstatedir}/log/httpd
    proxycachedir: ${localstatedir}/cache/httpd
</Layout>

This brings everything in-line with normal other installs. The configuration is as it was with the original Apache in ‘/etc/httpd‘ and the log, cache and pid file are all in ‘/var‘. Although I’m still having doubts about the datadir, I would have put it in ‘/var/www/‘ but on the normal OS X install it would be in ‘/Library/WebServer/‘. What do you think ?

PHP5 will be located in ‘/usr/local/php5‘, the php.ini file will be located in ‘/etc‘.

I hope to open up the new site tomorrow if all goes well…

It looks like we need an extra flag to compile properly namely the “--with-included-apr” option to force internal APR functionality and not from another package. The installation page has been updated accordingly !

There are more changes and bugs fixed besides this change, you can read all about them at the download page of apache, read the Changes file. I can’t link to it directly as it is dynamically altered to link to a mirror in your neighborhood.

I first did Postfix and Courier-auth as they would cause the least problems when it would go wrong. My backup mailserver would still receuve all mail and forward it to me when the mailserver is back online. It all went without a hitch, just did a restart of the programs and all was running as expected.

Apache posed an issue, how to compile and install, followed by compiling PHP without disturbing all the people looking at my sites. In the end it was simple. Compile and install Apache2, don’t restart Apache so the old version keeps running but the new software is available on disk. Then compile and install PHP using the new Apache installation files and when that is done restart Apache and all would be fine. Well that’s what I thought…

There was a small error in the modules that I included in the httpd.conf. Some of them, all concerning authentication, where rewritten and given different names. I was still trying to load the old ones as I didn’t update my httpd.conf to reflect these changes. So Apache2 wouldn’t start. I just commented out the old modules and added the new ones in my httpd.conf and presto, Apache 2.2.3 and PHP 5.1.6 are now running on my server, together with Postfix 2.2.3.

They’ve been running for almost a day now and I haven’t gotten any complaints yet.

If you are still running “ISP in a box” version 1 and want to upgrade but are still a bit afraid on how to do this let me know and I’ll help out.

Update:
Just found out there was an error, got a call on the phone from some of my friends that they couldn’t email anymore. When checking the logfiles I foud out I forgot a step after compiling and installing Courier auth:

sudo chmod o+x /usr/local/var/spool/authdaemon

In the logfile there was the error:

SASL authentication failure: cannot connect to Courier
      authdaemond: Permission denied

Which means I didn’t follow my own instructions !

Normally, for the Apple installed Apache, the logfiles would reside in /var/log/httpd, but I didn’t think and just followed the standard layout that was provided by the installation which directed the logfiles into /Library/Apache2/logs as you can see in the installation document. This means that the default weekly script (located in /etc/periodic/weekly) that takes care of the regular maintenance of your Mac, and rotates your Apache logfiles, didn’t take care of my new Apache2 logfiles.

So I’ve created a new script that rotates my Apache2 logfiles without having to change everything. You can download my apache.local script and copy it into your /etc/periodic/weekly/ directory, give it proper flags/rights to make it executable using:

sudo chown root:wheel /etc/periodic/weekly/apache.local
sudo chmod +x /etc/periodic/weekly/apache.local

Then test it out by running:

sudo /etc/periodic/weekly/apache.local

Now your logfiles won’t fill up your harddrive unnecessarily and by keeping smaller logfiles your Apache will run a bit better as well. Please note that your logfiles should have a filename that ends with log or it won’t work.

Note: please vote where the logfiles should reside (before I start updating the installation documents), in /var/log or /Library/Apache2/logs in the related forum topic. You need to register and wait for account activation if you haven’t already. Sorry, it’s needed to prevent those pesky spammers.

But it’s done, I’ve finally finished the instruction for installing (and compiling) MySQL 5, Apache 2 and PHP 5. Hope you are able to use them well.

• Installing MySQL
• Compiling and installing Apache 2
• Compiling and installing PHP 5

I’m currently working on the instructions for the mailserver as there are some tweaks needed to get that working with the current setup. There where some issues with Intel based Macs and SSL support but I’ve got that solved. Hope to get that finished in a very short time… (not naming dates here, getting careful… )

It’s the most simple way to do this without spending any money on official certificates or multiple ip-addresses. Especially that last point was the most difficult to solve. It seems, but I don’t know for sure as I’m not an expert on the subject, that it isn’t possible to configure more than one certificate per ip-address. Forgot the correct explanation and won’t go into wild guessing…

It works for me and I hope it will for you as well.

Note: People will get a warning that your certificate isn’t signed by a certified authority and if you use different domain names the browser will complain that the certificate and the domain don’t match. But if the user will accept the warning and continues the access to the website will be secured by SSL. This is very usefull if you don’t want your password to be send in the clear.

So here is the first public preview of the first pages of the new documentation. it’s not yet ready to be used properly as I only got MySQL and Apache2 covered. PHP is coming before the end of the week. But I wanted to see how you like the new way of documenting. Hope you like it…

Two more remarks:

• I’ve created a page to keep you informed on the funding of the new Intel based Mac mini. Donations and AdSense income are going strong and I think I can order an Intel based Mac mini before the end of the summer. I you want to contribute to this effort as well, use the PayPal button on the right side of the page.
• I don’t like the phrase “ISP in a box” too much but I still can’t think of another one that covers what I’m documenting here. So I wanted to ask you, can you think of a better phrase or slogan ? Or do you think “ISP in a box” is good enough ? Please let me know what you think.

First download Apache HTTP server version 2.0.55. Unpack it into a directory and open the file config.layout for editing and add the following code at the end of the file.


<layout ServLog>
prefix: /Library/Apache2
exec_prefix: ${prefix}
bindir: ${exec_prefix}/bin
sbindir: ${exec_prefix}/bin
libdir: ${exec_prefix}/lib
libexecdir: ${exec_prefix}/modules
mandir: ${prefix}/man
sysconfdir: ${prefix}/conf
datadir: ${prefix}
installbuilddir: ${datadir}/build
errordir: ${datadir}/error
iconsdir: ${datadir}/icons
htdocsdir: ${datadir}/htdocs
manualdir: ${datadir}/manual
cgidir: ${datadir}/cgi-bin
includedir: ${prefix}/include
localstatedir: ${prefix}
runtimedir: ${localstatedir}/logs
logfiledir: ${localstatedir}/logs
proxycachedir: ${localstatedir}/proxy
</Layout>


This configures the build and configuration process to mimic the configuration used by ServerLogistics and keeps everything in place as it is. If you’ve done that then open a Terminal session, change to the directory in which you unpacked the source code and edited the config.layout file and run the following command:

./configure --enable-layout=ServLog --enable-mods-shared=all --with-ssl=/usr --with-mpm=prefork --enable-ssl --enable-dav --enable-cache --enable-proxy --enable-shared --disable-static --disable-unique-id --disable-ipv6 --enable-logio --enable-deflate --with-ldap --with-ldap-include=/usr/include --with-ldap-lib=/usr/lib --enable-ldap --enable-auth-ldap --enable-cgi --enable-cgid --enable-suexec


This will create and configure the Makefile for actually building the Apache webserver like the package from Server Logistics. When it’s done just execute the next command:

make

When that’s finished and you are sure (made a backup of your system and all) you can issue:

sudo make install

Stop and start Apache and you are running the new 2.0.55 version. Don’t do a restart as that just reloads the configuration. Use the Apache preference pane you installed earlier to stop and start it or use the apachectl command in the Terminal as a root user.

It was quite easy doing the migration, just copying the HTML/PHP files, making a backup of all the databases and restoring them on the mini for the web part. For the mail server I used postfix admin to create all the mailboxes and aliases for all the domains. Then made backups from the original server and restored them on the new mini.

I did some tests on the web part, to see if everything was configured as it should and tested the mail server to see if it didn’t become another spam relay server and it blocked unwanted spammers from sending mail via my server. I asked a friend to try abuse my server and used the relay service at www.abuse.net to check independently. It all worked out. The server is secure, still could use some tweaking but I will report on that later.