M
Mike Jacoubowsky
Here's the scoop. I've originally had a disk-based web on my local hard
drive, which I've published *to* (instead of from) as a "remote" site.
That's meant that I've been editing live, on the ISP's website, and then
publishing back to my laptop. Not a good way to do things.
So, thanks to help from Steve Easton, I've now got my site published to my
laptop, with front page extensions etc (using IIs). So the local website at
this point remains the ISP server, and the laptop is still the "remote."
So my next step is presumably to simply reverse the publishing direction?
Set the laptop as the "local" and the ISP as the "remote" and publish away?
Thanks-
--Mike Jacoubowsky
Chain Reaction Bicycles
www.ChainReaction.com
Redwood City & Los Altos, CA USA
drive, which I've published *to* (instead of from) as a "remote" site.
That's meant that I've been editing live, on the ISP's website, and then
publishing back to my laptop. Not a good way to do things.
So, thanks to help from Steve Easton, I've now got my site published to my
laptop, with front page extensions etc (using IIs). So the local website at
this point remains the ISP server, and the laptop is still the "remote."
So my next step is presumably to simply reverse the publishing direction?
Set the laptop as the "local" and the ISP as the "remote" and publish away?
Thanks-
--Mike Jacoubowsky
Chain Reaction Bicycles
www.ChainReaction.com
Redwood City & Los Altos, CA USA