Moving sites to new hardware

[Peter Harbeson]

Thanks -- once I got over my initial consternation at having to do this 
at all, it was easy. My script wasn't sophisticated at all; it simply 
found every instance of the old path and replaced the relevant portion. 
It didn't seem worth developing the script further because I expect 
this to be a pretty unusual event. (My first posting took place during 
my "initial consternation" periond!)

-Pete Harbeson

On Sunday, December 29, 2002, at 12:35 PM, matt neuburg wrote:

>
> Once you have a list of all the places where absolutely pathnames are 
> saved in the database it is easy to write a script that changes them 
> all. That takes 3 seconds, not 3 hours. I have such a script, and it 
> runs on startup; if there's a problem, it asks me for instructions, I 
> give them, it adjusts all the pathnames, and away we go. The only 
> problem is that my attempts to automate this process *completely* - 
> that is, to detect automatically exactly how much of each pathname is 
> wrong - have never quite succeeded; thus human intervention is 
> necessary. That, of course, might not be acceptable (because one might 
> move one's copy of Frontier to a remote machine). m.
>
> matt neuburg, phd = matt at tidbits.com, http://www.tidbits.com/matt
> pantes anthropoi tou eidenai oregontai phusei
> Subscribe to TidBITS! It's free and smart. http://www.tidbits.com/
>
>