For this example, we are going to add a virtual host for the snow.ftd host.

Jetty Setup

Jetty makes it really easy to configure virtual hosts for a context.

The configuration file in Railo Express at {railo-express-directory}/contexts/railo.xml already has the configuration setup to start us off:

<!-- virtual hosts
<Set name="virtualHosts">
	<Array type="String">
		<Item>www.myVirtualDomain.com</Item>
		<Item>localhost</Item>
		<Item>127.0.0.1</Item>
	</Array>
</Set>
-->

Uncomment the block of code and change the item to match the snow.ftd host name like so:

<!-- virtual hosts -->
<Set name="virtualHosts">
	<Array type="String">
		<Item>snow.ftd</Item>
	</Array>
</Set>

Local Host Setup

I already posted instructions for adding local hosts to your Snow Leopard. You can follow the directions there to setup your desired host. In linux you can modify your hosts file in a similar fashion. There may even be a way to change your hosts file on windows, although I have never done so.

Testing

Once the Jetty config and the local hosts have been updated, restart Railo—if it is running—and go to snow.ftd:8888 in your browser. You should see the same page available at localhost:8888.

And you are done! You can now add as many hosts as you need!

Using the dscl Utility

With the wonder of Google searching and the generous comments of others I found out about the dscl utility.

Listing Host Entries

To see what is listed for your hosts at any time just run this command:

dscl localhost -readall /Local/Default/Hosts

Adding a New Entry

In this example I am going to have the snow.ftd host point to my 127.0.0.1 IP address:

sudo dscl localhost -create /Local/Default/Hosts/snow.ftd IPAddress 127.0.0.1

You should now be able to ping snow.ftd and have it resolve to your local computer.

Removing an Existing Entry

If you decide you do not want an entry anymore just run this command to remove it:

sudo dscl localhost -delete /Local/Default/Hosts/snow.ftd

Reading the BSD Flat File

It was also noted that you can read the BSD flat file using this command:

dscl localhost -readall /BSD/local/Hosts

Step 1: Download Needed Files

The first step is to download all the files you will need. Since the downloads usually take some time we’ll get them out of the way first.

For my installation I wanted to get more familiar with the Server edition of Ubuntu and to require fewer resources. You should be able to do a similar installation with the Desktop edition.

• Download VirtualBox – The official VirtualBox download page.
• Download Ubuntu – To download the Server edition you will need to find a mirror that hosts the installer images. Once you find a mirror navigate to the 9.10 directory and find the download link for the ubuntu-9.10-server-i386.iso file.
• Download ColdFusion – The official Developer Edition Download is available on the Adobe ColdFusion page. Download the Linux 32 bit installer.

Step 2: Install VirtualBox

Once you have downloaded all the files, run the VirtualBox installer.

If you would like to learn more about VirtualBox the installation comes with a user manual or you can download a pdf copy from their download page.

Step 3: Create an Ubuntu Virtual Machine

Click the New icon in VirtualBox to start the wizard for adding a new VM.

1. Click Next to start the wizard.
2. Enter Ubuntu CF for the Name of the VM.
3. Select Linux and Ubuntu in the OS Type drop downs.
4. Click Next.
5. Click Next to accept the default amount of RAM. (You can adjust if you want to…)
6. Click Next to create a new hard disk image to use for the VM.
   1. Click Next to start the wizard .
   2. Click Next to create a dynamically expanding storage.
   3. Click Next to accept the default name and size.
   4. Click Finish to accept the choices for the disk image.
7. Click Finish to end the wizard.

Step 4: Install Ubuntu

Now that there is a VM setup to hold the guest Ubuntu system we need to install Ubuntu on it.

In VirtualBox Double Click on the Ubuntu CF listed in the left column to start up the VM. Since this is the first time you are starting the VM it will bring a up a First Run Wizard to guide you in setting up the new VM.

1. Click Next to start the wizard.
2. Change the Media Source to Image File and click the Other... icon.
   1. Click the Add icon along the top.
   2. Select the ubuntu-9.10-server-i386.iso file we downloaded earlier.
   3. Click Select with the ubuntu-9.10-server-i386.iso item selected.
3. Click Next to continue.
4. Click Finish to end the wizard.

The VM should now startup and bring up the installation the Ubuntu. I’m not going to go into the details of installing Ubuntu here, so just continue with the next step once Ubuntu installation is complete. Also, since we are going to be using apache you may wish to have the setup create a LAMP server configuration when choosing features or you can install it manually afterwards.

Step 5: Setup Guest Additions

In order to have the Shared Folders work we will need to install the Guest Additions.

Before we install the Guest Additions we will need to install dkms:

sudo apt-get install dkms

To mount the Guest Additions disc image to the VM press Command + D or select Devices > Install Guest Additions... from the VM menu. Then install the Guest Additions by running:

cd /cdrom

sudo sh ./VBoxLinuxAdditions-x86.run

Step 6: Setup Shared Folders

One of the goals when creating the virtual machine was to be able to edit the files natively but run them on the guest operating system that reflects the production environment.

With shared folders we are able to use a local directory as a share on the guest VM.

Before we add the shared folder we need to have a folder to share. For this example I’m using the directory I created at /Users/randy/Documents/cf9/.

With the VM powered off edit the Settings and select the Shared Folder icon.

1. Click the Add a new shared folder definition icon on the right side.
2. Enter the Folder Path (/Users/randy/Documents/cf9/) or select Other... from the drop down and locate the directory.
3. Enter the name you would like the share to be referenced as in the Folder Name field. In this case I am going to call it cf9.

Now that we have the shared folder available to the VM we want it to mount the share each time the VM starts. To do this we startup the Ubuntu VM and edit the /etc/fstab file and add the following line at the end of the file (note that you will need to change the username to match your user):

cf9	/home/randy/Documents/cf9	vboxsf	uid=randy,gid=users	0	0

You will also need to create a blank directory at /home/randy/Documents/cf9 that the share will mount to.

The next time your VM is started it should have access to /Users/randy/Documents/cf9 on the host machine at /home/randy/Documents/cf9 on the guest machine.

Step 7: Enable Port Forwarding

To setup the port forwarding you will need to stop the VM. In the terminal run the following commands to setup the port forwarding. (Note that "Ubuntu CF" needs to match the name of the VM created above.)

VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/Protocol" TCP
VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/GuestPort" 80
VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/HostPort" 8580

This will change the VM settings to have the guest port of 80 (which is the default apache port) of the guest forwarded to port 8580 on the host. Without this you would not be able to talk to the guest operating system.

Step 8: Install ColdFusion

Since we already downloaded the installer for ColdFusion we just need to get that file to the VM. Luckily we already setup a shared folder so if you move the installer to the /Users/randy/Documents/cf9/ directory it will be available in the VM.

To run the ColdFusion installer:

cd /home/randy/Documents/cf9/

chmod +x ColdFusion_9_WWE_linux.bin

sudo ./ColdFusion_9_WWE_linux.bin

This should start the installer. During the installation, apache should be configured to run with ColdFusion.

Step 9: Test Environment

To test that the development environment is working correctly you should be able to place an index.cfm file in your /Users/randy/Documents/cf9/ directory. Make sure that you place some CFML in the file to test that ColdFusion is doing it’s thing. Then visit http://localhost:8580/ in a browser on your host to test out the new development environment!

With the wonderful advances in the cloud I decided to see what it could do for me. After doing a little searching I found a post or two about it and I decided to try it out myself.

To use Amazon’s S3 for the vault I need to have it be mounted as a drive. I chose to use a product called Jungle Disk to mount and manage my S3 account. Jungle Disk has clients for all the operating systems and a version for portable drives that has all three clients.

Once I had setup a bucket with Jungle Disk I was ready to create my vault with Aperture. The way that Aperture is programmed it won’t allow you to directly setup the vault on a network drive. To get around that I create the vault onto the desktop. Once the vault is created you will notice that it has the locked symbol next to it. I closed Aperture and removed the locked status from the file. Then I moved the vault onto the S3 drive.

I had about 35GB library of photos when I created the vault. Since this is all going over the internet it is going to take a while for all the files to copy over, which is to be expected. I was luckly on a university connection so the wait wasn’t as long as it was for some.

After the files all successfully copied over to the S3 account load up Aperture. Right click on the vault that was just created and select the Update Vault Path… From there you should be able to browse to your S3 network drive and select your vault.

When I had taken some more pictures and went to update the vault I found the big reason that I probably would not use the S3 for anything but periodic (quarterly or semi-annually) backups. When I updated the vault it seemed to want to touch and/or copy every file. If you are on a local drive this wouldn’t be much of a problem, but since you are doing this over the internet it seemed to take about as long as the original move of the library. It might not have taken as long since I just left it working overnight I didn’t know for sure.

Just remember, if you do plan on using the S3 for aperture not only are you paying for the space, which is very inexpensive, but you are also paying for each request for a file so it does add a few dollars each time you do a vault update. Overall I would still use it as a periodic off-site backup but would not rely upon it for my day-to-day backups.

Something that I found out in the recent months and finding very useful is the reverse-i-search. By pressing ctrl + r in the terminal (works at least in ubuntu and OS X, probably all real terminals) you are given a console line like the following:

(reverse-i-search)`':

As you type the terminal will search through your terminal history and locate any commands that contain what you search.

For instance if you type ssh it will start searching through the history and show you the last one that you used that had ssh in the command. If the first result isn’t the one that you are looking for you can press ctrl + r to keep the search going and cycle back through your history.

I am still amazed by all the things that I am learning about *nux operating systems and I am only touching the surface.