On Fri, 5 Oct 2001, birgit kellner wrote:
> Until now, the site was not officially online, which meant that all editing
> could be done directly on the original files on the server.
> Now it's public, which of course means I should perform all editing
> operations offline - I'm pondering over what's the most efficient way to do
> that, and how to use perl in what would basically amount to copying data
> structures back and forth, changing directory parameters in the process and
> comparing file versions (by date and time, presumably). This is to apply to
> all file types included - html, pl, cgi.
If you can, set up a second internal domain (or even just an IP alias),
and use it as a staging server, and do all of you development there. You
can set up multiple virtual domains to do this, or even a second machine.
Once everything is tesed and functional, then you move what you need over
to the production system, using rsync or something like that.
-- Brett
http://www.chapelperilous.net/
------------------------------------------------------------------------
Despite all appearances, your boss is a thinking, feeling, human being.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
