eea3a7d7d0
Include information on basic use of the FrontPage Extensions.
<Makefile>
Modify the METALOG generation so the installed frontpage binaries
have the ownerships expected by ap-frontpage. (namely, ${BINOWN} and
${BINGRP})
<TODO>
General update of the progress to date.
Notable item: successful publishing of a site from MS-FrontPage 2000
to the FrontPage Enabled Apache site on NetBSD/alpha 1.6.1_STABLE.
31 lines
955 B
Text
31 lines
955 B
Text
===========================================================================
|
|
$NetBSD: MESSAGE,v 1.2 2003/06/13 05:32:06 schnoebe Exp $
|
|
|
|
This port requires an Frontpage enabled Apache web server.
|
|
|
|
../../www/ap-frontpage provides a replacement (non-Microsoft)
|
|
loadable module for supporting FrontPage.
|
|
|
|
For the FrontPage Server Extentions to operate properly, the
|
|
following directives need to be set in your Apache web server
|
|
Configuration.
|
|
|
|
At the global level:
|
|
|
|
# Enable FP Extensions Client publish
|
|
FrontPageEnable
|
|
# Enable FP Extensions Admin web site
|
|
FrontPageAdminEnable
|
|
|
|
At the <Directory> level:
|
|
|
|
AllowOverride AuthConfig Limit FileInfo Options Indexes
|
|
|
|
FYI: The owsadm.exe program expects to find the following directives
|
|
in the configuration file it uses for (sub)site enablement:
|
|
|
|
ServerRoot
|
|
ResourceConfig
|
|
AccessConfig
|
|
|
|
===========================================================================
|