K
Kevin Lucas
I want to be able to use a single Microsoft Personal Web Server (PWS)
running on Win 98SE to host FrontPage webs and non-FrontPage webs
simultaneously. One of the reasons is that I want to be able to publish
simple FP sites or non-FP sites by pushing them to the Web server rather
than pulling them from the web server PC because it is not normally easily
accessible. And as I understand it PWS only allows authoring such as that by
FrontPage from its own host PC rather than any remote PCs.
This would allow me to migrate away from FP to something that will allow FTP
(and hence get round PWS's authoring limitations).
My PWS has the Frontpage extensions and I see from this newsgroup that I
shouldn't really FTP the non-FP webs to the server. So I wondered:
- whether I could still make the two types of web coexist by setting the PWS
manager to control a folder quite outside my standard PWS folder-set (which
is in Inetpub/wwwroot) and FTPing my non-FP webs into this separate folder
- or could I use the Publishing Wizard within the PWS manager to load a
non-FP web into the standard web server folders? Would it look after the
issues of the FP extensions successfully as it does so? (The downside here
is that I have to do this from the PWS host PC)
- or would the Microsft Web Publishing Wizard for example take due account
of the FP extensions on the server and somehow handle the fact the webs I'm
publishing aren't from a FP environment without damaging the extensions in
the process?
Even if I used a web server other than PWS I'd still need the FP extensions
until I can migrate all my existing webs and then I'd presumably be back to
the original problem of needing the extensions while wanting to publish
sites that don't use them.
I'd prefer to avoid running two web servers on different ports if possible.
Sorry this is a bit complex to explain but is it obvious to anyone how I
should go about this please?
Many thanks for any help you can give.
Kevin Lucas
running on Win 98SE to host FrontPage webs and non-FrontPage webs
simultaneously. One of the reasons is that I want to be able to publish
simple FP sites or non-FP sites by pushing them to the Web server rather
than pulling them from the web server PC because it is not normally easily
accessible. And as I understand it PWS only allows authoring such as that by
FrontPage from its own host PC rather than any remote PCs.
This would allow me to migrate away from FP to something that will allow FTP
(and hence get round PWS's authoring limitations).
My PWS has the Frontpage extensions and I see from this newsgroup that I
shouldn't really FTP the non-FP webs to the server. So I wondered:
- whether I could still make the two types of web coexist by setting the PWS
manager to control a folder quite outside my standard PWS folder-set (which
is in Inetpub/wwwroot) and FTPing my non-FP webs into this separate folder
- or could I use the Publishing Wizard within the PWS manager to load a
non-FP web into the standard web server folders? Would it look after the
issues of the FP extensions successfully as it does so? (The downside here
is that I have to do this from the PWS host PC)
- or would the Microsft Web Publishing Wizard for example take due account
of the FP extensions on the server and somehow handle the fact the webs I'm
publishing aren't from a FP environment without damaging the extensions in
the process?
Even if I used a web server other than PWS I'd still need the FP extensions
until I can migrate all my existing webs and then I'd presumably be back to
the original problem of needing the extensions while wanting to publish
sites that don't use them.
I'd prefer to avoid running two web servers on different ports if possible.
Sorry this is a bit complex to explain but is it obvious to anyone how I
should go about this please?
Many thanks for any help you can give.
Kevin Lucas