sync/ports
1
0
Fork 0
mirror of https://git.freebsd.org/ports.git synced 2025-06-07 05:40:30 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add better explanations. Ideas from barbish@a1poweruser.com

Browse source
This commit is contained in:
Martin Blapp 2002-05-23 22:25:33 +00:00
parent 03f189ed5b
commit 83fb4c4424
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=59827
1 changed files with 31 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
www/mod_frontpage/pkg-message
View file

@ -1,35 +1,59 @@
************************************************************************ ************************************************************************
1.)
Check your httpd.conf, if you have included a ResourceConfig and Check your httpd.conf, if you have included a ResourceConfig and
AccessConfig. If you do not have these files, you'll have to add AccessConfig. If you do not have these files, you'll have to add
these lines to make frontpage extensions working properly: these lines to make frontpage extensions working properly. These
lines are commented out in a default config, so you'll have to
activate them again. If you have some real ResourceConfig and
AccessConfig, you can skip this part.
ResourceConfig /dev/null ResourceConfig /dev/null
AccessConfig /dev/null AccessConfig /dev/null
2.)
You'll also need to change AllowOverride under You'll also need to change AllowOverride under
<Directory "/usr/local/www/data"> ( or the place where you <Directory "%%PREFIX%%/www/data"> ( or the place where you
moved your webservers ) from None to at least: moved your webservers ) from None to at least:
AllowOverride AuthConfig Limit Indexes Options AllowOverride AuthConfig Limit Indexes Options
Don't use "AllowOverride All" if you have a server environment
with customers, since this can be a security risk If you use
this, they can enable mod_php4 etc. themself with .htaccess files.
3.)
You can turn off/on the extensions and the frontpage administration You can turn off/on the extensions and the frontpage administration
per site in httpd.conf and per virtual server. FrontPageAdminDisable per site in httpd.conf and per virtual server. FrontPageAdminDisable
is the default if no option is given. is the default if no option is given.
FrontPageEnable # Enable Frontpage Extensions FrontPageEnable # Enable FP Extensions Client publish
FrontPageDisable # Disable Frontpage Extensions FrontPageDisable # Disable FP Extensions Client publish
FrontPageAdminEnable # Enable Frontpage Extensions fpadmcgi.exe FrontPageAdminEnable # Enable FP Extensions Admin web site
FrontPageAdminDisable # Disable Frontpage Extensions fpadmcgi.exe FrontPageAdminDisable # Disable FP Extensions Admin web site
If no key word options are present in the httpd.conf file the default of
FrontPageDisable and FrontPageAdminDisable is used resulting in a working
Apache environment where the complete frontpage environment is disabled.
4.)
After you have made these changes, you'll have to execute: After you have made these changes, you'll have to execute:
%%PREFIX%%/frontpage/version5.0/fp_install.sh %%PREFIX%%/frontpage/version5.0/fp_install.sh to build the base
apache/frontpage web site and to setup frontpage users and admins.
You can also run this to add virtual hosts to the apache/frontpage
system.
5.)
If you have installed the port in another PREFIX than "/usr/local" If you have installed the port in another PREFIX than "/usr/local"
you have to create a symlink. Microsoft has hardcoded the local you have to create a symlink. Microsoft has hardcoded the local
path in their binarys. If you do not use fp_install.sh, you have path in their binarys. If you do not use fp_install.sh, you have