In uk.net.web.authoring John Bokma <john@castleamber.com> wrote:
> axel@white-eagle.invalid.uk wrote:

>> Rather than relying on back-ups of a site, a far better policy is to
>> maintain a development version of the site on your own machines and
>> refresh the production site from the development site as and when
>> required.

> See: <http://johnbokma.com/windows/apache-virtual-hosts-xp.html>
> on how to create local versions of your site(s). (Windows XP).

Hi John... greetings in a different forum than usual.

A good guide.

The approach I adopted (on MACOSX) was to assign different private IP
addresses in /etc/hosts and configure httpd.conf accordingly.

Your approach makes more sense in using 127.0.0.1 as the one base
IP address when only using a single local machine, which I'm doing
at the moment... it saves having to edit configuration files when
moving to a different network (a couple of months ago I had to
switch to a 10.0.1 network).

Although I have a development site on my local machine which I use
to check out things before uploading... I do my real development a
stage before that by using Makefiles, the htp 1.15 HTML pre-processor
(old, but it works just fine) and various perl scripts to create
the deveopment site, or parts thereof. In other words I write as
little HTML as possible.

Axel