Way back in January I gave a sneak peek of an Apache article I had written for the Fusion Authority Quarterly. During the welcome reception of the Adobe Community Summit (last night) Terrance Ryan came up and said he had read (and enjoyed mind you) my article. Up until that moment I didn't even know it was released.

If you're interested in understanding Apache more I encourage you to check out my article. While you're at it, why not purchase a subscription to FAQU? It's an excellent magazine available in print and PDF versions.

Over the weekend I was finishing the first draft of my Apache Essentials for ColdFusion Developers article in the next issue of the Fusion Authority Quarterly Update. I use Apple's Pages to do most any kind of writing and while spell checking the article, Pages prompted me with the following:



While the spell checker couldn't have been more "off," I did get a chuckle out of the suggestion.

UPDATE
With the 8.0.1 update of ColdFusion, OS X 10.5 Leopard is natively supported. To install ColdFusion you simply download the 32-bit or 64-bit version of the OS X installer and walk through the installation screen. The steps I outlined below, getting a custom compiled version of the Apache 2.2.x connector are no longer necessary as CF8 ships with an appropriate connector.

----------------

I've had ColdFusion 8 running on OS X 10.5 (Leopard) and hooked to Apache 2.2.6 for a while now. However, two things have occurred that are prompting me to write this blog entry. First, I've gotten several questions on exactly how I got things working - even with the other blog entries that outline a similar process. Second, I ran into an odd issue Friday when configuring everything on my new work MacBook Pro.

This is a small part of an article I'm writing for the Fusion Authority Quarterly Update Volume 2 Issue 4, due out in February. The information is so important I felt it could not wait, and am publishing this with permission from Fusion Authority. In this blog post, I will discuss the installation issue and its resolution, and provide my consolidated, easy steps for getting ColdFusion 8 hooked to Apache 2.2.x on Leopard.

[More]

Search Engine Safe URL's (often abbreviated SES) are attractive to Web developers and business owners because they "pretty up" the browser address bar, help search engines crawl through site content, and generally make it easier to share URL's to content deep within a Web site. The advantages to using SES URL's are covered exhaustively throughout the Web if you want more reasons why you should use them. For information on how to set up and configure Apache's mod_rewrite including the creation of SES URL's for a Mach-ii site, read on...

[More]

Throughout the parts of this text I've used TortoiseSVN to perform all repository actions. This was mainly due to the simplicity and ease of use TortoiseSVN affords. TortoiseSVN is also handy when versioning assets that aren't code-related like spreadsheets and general documents. When working with code - ColdFusion for instance - there are other Subversion clients that work just as good as TortoiseSVN and don't require you to leave your development environment to request repository updates or commit changes. One such tool is Subclipse which is built on the open-source Eclipse platform. Eclipse is an extremely popular Java-based programming tool that works with just about every modern programming language. I use Eclipse and Eclipse plugins like CFEclipse on a daily basis to manage my code. In the this section, I discuss installing, configuring, and using Subclipse, the Subversion plugin for Eclipse.

[More]

At the end of Part 2 we briefly looked at Apache's logging of Subversion's "traffic." We'll revisit this topic in this section discovering a better way to configure logging. We'll also address repository security adding a couple DAV directives that create authenticated repository access. Let's get right to it.

[More]

In Part 1 I walked through the installation of the Apache Web server. In Part 2 I covered the installation of Subversion and the integration of Subversion and Apache. This involved configuring an Apache Virtual Host to handle all the requests that come from the Subversion sub-domain (svn.yourcompany.com:81). We also configured dedicated logging for all Subversion HTTP requests through appropriate Virtual Hosts directives. Finally, we looked at browsing the Subversion repositories via a Web browser, but since we hadn't created any repositories, this task was pretty unexciting. In this section I'll discuss the installation of TortoiseSVN, a popular client-side Subversion tool. Through TortoiseSVN we'll be able to create our first repository and perform our first repository import.

[More]

In Part 1 I walked through the installation of the Apache Web server. With that step complete it's time to install the Subversion server and integrate Subversion and Apache. Once we've completed these steps we'll have our source control server environment in place and we'll be ready to install some Subversion client tools.

[More]

Part 1 of this text is going to walk you through installing and configuring the Apache Web server in preparation for hooking Apache and Subversion together.

[More]

During the past two weeks I have worked on a new paper outlining the process of installing and configuring a development environment with Apache, Subversion, TortoiseSVN, and Subclipse. Over the next day or two I will be posting the individual parts of the paper as a blog series. For those that prefer to read offline, the entire text (60 pages and 91 screenshots) is available as a PDF download (see below). This blog post kicks off the 5 part series with the Introduction.

Click here to download Configuring a Development Environment with Apache, Subversion, TortoiseSVN, and Subclipse or click the "more" link to begin with the introduction.

[More]