This is a little trick I’ve picked up that helped me out quite a bit, especially when developing Wordpress sites where you need to get the paths and URLs right for everything to work properly.

The scenario

You’re hired to do the redesign of an existing website (example.com). Your client wants to move their website to your hosting (or new hosting) when the redesign goes live. You’ve agreed on a seamless transition from old to new on one sunny Monday morning in a months time.

So you get to work on the site in your chosen development area, demo it to the client, they’re happy and you transfer the site to the newly configured hosting space on your server, however the name servers for example.com haven’t been changed yet, it’s only Friday and the redesign isn’t going live until Monday, but you’re a contentious developer and you want to test the new design to ensure everything is working as expected in the live environment.

What do you do?

Our goal

We’re going to edit the hosts file on our Mac to make our servers IP address (e.g. 70.26.55.80) resolve to example.com, just like what a DNS server does when example.com’s name servers have been changed to point to the new hosting.

Configuring the server

All server configurations are different but the principle is generally the same, we need to find out/set our example.com to appear in the web browser when we visit our example IP of 70.26.55.80. For this example I’m going to explain the process on a Plesk driven server (from this you should be able to get an idea of how this would be achieved through other management software packages).

• Configure your web space for example.com and upload all your files to it
• Login to Plesk
• Select Server from the left-hand menu
• Go to the IP Addresses – This should present you with a list of IP addresses assigned to your server, when you configured the hosting for example.com you will have selected one of these IP addresses (you may even only have one IP address in this list)
• For each IP address there’s a column titled Hosting with a link showing the number of domains assigned to that IP address, click the link that corresponds with the IP address you selected for the web space
• Select example.com and click Set As Default - You can only select one default domain to be displayed if you visit that IP address in a browser
• Make a note of the IP address (e.g. 70.26.55.80)
• Visit 70.26.55.80 in a web browser – You should be presented with your newly uploaded site for example.com

Editing the hosts file

Mac’s have a hosts file that we can edit to make 70.26.55.80 resolve to example.com just as if the name servers for example.com had already been changed (obviously this only effects the Mac you are on).

I’m sure you’ll be able to do this on a PC as well but don’t ask me how, I’m a Mac man.

• Open a Terminal
• Enter sudo vim /etc/hosts then enter your administrator password

This will open the hosts file in the vim editor. You should see something like this:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1             localhost
fe80::1%lo0     localhost

To edit the file press ‘a’, cursor down to the bottom of the list and enter:

70.26.55.80       example.com

Press ‘esc’ then enter ‘:wp’ to write and quit vim.

If you now visit example.com in your web browser it should resolve to 70.26.55.80 (the new hosting) and you can test your newly designed site in its live environment.

Now all that has to be done to make the site seamless go live on Monday is change the name servers for example.com to point to your hosting and you can guarantee that everything will work.

Important note: Remember to take the entry for example.com out of your hosts file when you have finished testing, otherwise you may end up seeing a false representation of what is actually being displayed at that domain when the name servers are changed!

Final Tip: Instead of removing the line completely from your hosts file simply add a # to the beginning of the line. This “comments out” the line and stops it from being applied. If this is a process that you are going to use regularly in the future then the line is already in your hosts file and you can simply remove the # and change the domain name when you need to.

I installed Snow Leopard the day after it came out like so many others. It was a smooth installation for me with only Dropbox breaking, however this was soon fixed by installing the latest beta and I’ve not had a problem since.

Apple have been pushing Snow Leopard as giving a significant improvement on speed, which to be honest I haven’t really noticed. In fact the only real obvious difference I’ve noticed between using Snow Leopard on my MacBook and Leopard on my iMac is spaces and expose which feel more refined in Snow Leopard.

There area a few annoying issues that I have found with Snow Leopard however, and these may just be specific to my situation.

My setup at home is a MacBook connected to the Apple 24” Cinema Display and here’s a list of the problems I’ve been having.

Desktop icons become un-clickable

If my MacBook is in stand by and I connect it to my cinema display, the desktop extends fine, however any icons/files I have on the desktop become un-selectable or clickable. I can’t even drag a selection around the icons. It’s as if the selectable area of the cinema display is now the same size as that of the MacBook.

Cursor goes weird when waking from sleep

I’ve noticed the spinning beach ball cursor glitching when coming out of standby. It kind of breaks in half and pixellates.

Trackpad gestures behave differently/weirdly

This one is difficult to explain. On the trackpad of my MacBook the four finger gesture down performs expose and the four finger gesture up reveals the desktop. On Leopard, if you dragged four fingers down to activate expose and lifted your fingers off it would sit there. Then you could either drag your fingers up or down to revert back. This behavior was the same for dragging up to reveal the desktop.

However in Snow Leopard, if you drag four fingers down to activate expose, you have to drag four fingers up to revert back. If you drag four fingers down again, it reverts then activates expose again. It’s weird, try it yourself!

iTunes auto-launches when using the play/pause keyboard shortcut

This is extremely annoying, and I don’t know if you can turn it of?

If I’m listening to Spotify, and click the play/pause shortcut on the keyboard, iTunes auto-launches and plays over the top!

iChat video quality is appalling due to port restrictions

Apple boasted that iChat video conversation quality had improved in Snow Leopard. However, I’ve not found this to be the case. Under Connection Doctor it has a new network status report that checks your connectivity. On mine it says port restricted. However, after searching Apples forums (with no joy) and opening my router to the world I still can’t get this message to disappear and it appears to be having an effect on the video quality that I’m getting, which isn’t good when you record a video podcast over iChat!

iChat record format is different and doesn’t work with iMovie

Just to top off the iChat annoyance of bad video quality, after recording an interview, iChat outputs the recording in a different format to what Leopard was using, which is fine, however iMovie won’t import and thumbnail this new format, which means I have to decompress the video using Quicktime before I can start editing it in iMovie!

Conclusion

All in all Snow Leopard seems to have caused more problems that it’s solved, in fact Leopard feels much more stable to me and seen as I’m still using Leopard on my iMac at work the differences are noticeable. What have your experiences with Snow Leopard been like? Do you regret the upgrade?