Frontpage perils

[Nick Rogness]

On Fri, 1 Aug 2003, Mark wrote:

> I just installed apache+mod_ssl-1.3.28+2.8.15 (FreeBSD 4.7R). Having
> some serious trouble integrating Frontpage 5, though. I installed the
> package, and it seemingly integrated just fine:
>
> lynx --head --source http://asarian-host.net:90/overview.html
>
> Server: Apache/1.3.28 (Unix) FrontPage/5.0.2.2623 PHP/4.3.1
> mod_ssl/2.8.15 OpenSSL/0.9.6g mod_perl/1.26
>
> So far, so good; then I ran the install script:
>
> asarian-host: {root} % /usr/local/frontpage/version5.0/fp_install.sh
>
> ------------------------
> Step 3.  Upgrading/Installing the extensions
>
> Checking for previous versions of FrontPage Server Extensions to
upgrade...
> You have an older version of FrontPage Server Extensions installed
> (4.0). Would you like to migrate these settings to version 5.0 now (y/n)
> [Y]?
>
> Checking for existing web servers to upgrade...
>
> Existing web servers were found; do you want to upgrade them now? (If
> you answer "no", you can safely run this script again and answer "yes"
> to upgrade your servers later.)
>
> Upgrade now (y/n) [Y]?  y
>
> All existing servers will now be upgraded:
>
> Upgrading using configuration file:
> /usr/local/frontpage/someone.asarian-host.net:80.cnf
> Verifying web server configuration...
> This version of FrontPage Server Extensions does not suppport
> apache servers.  We only support patched apache servers.
> ------------------------

>
> Say what? :) Does not support apache servers? Then what have I been
> compiling for, the last half day? I must be missing some step in the
> process. Does anyone know what I am doing wrong?
>

	All you should have to do is:

	# cd /usr/ports/www/apache13-modssl && make install
	# cd /usr/ports/www/mod_frontpage && make install

	If all goes well you should have everything you need installed.  I
	personally don't use the fp_install.sh script...I think it sucks.
	If I need to install frontpage extentions on a website I do the
	following:

		1) Add the VirtualHost to the main httpd.conf file (must
		   be in the main httpd.conf file):

			<VirtualHost 64.251.173.41:80>
			  ServerName www.domain.com
			  ServerAlias domain.com
			  DocumentRoot /home/jim/public_html
			  UserDir disabled
			</VirtualHost>

		2) Install extensions with the owsadm.exe tool (execute
		   the line wrap):

			# cd /usr/local/frontpage/version5.0/bin
			# ./owsadm.exe -o install -u jimfpuser -p 80 \
			-m "www.domain.com" \
			-servconf "/usr/local/etc/apache/httpd.conf" \
			-xuser jim


		3) Restart apache:  # apachectl restart


	It should prompt you for a password...which is the FRONTPAGE
	password for the FRONTPAGE user 'jimfpuser' as seen above.
	jimfpuser doesn't need to exist anywhere on the systemm, but you
	will need to use it with the frontpage client to connect to
	www.domain.com.

	Now, there are some gotcha's with frontpage.  First off,  make
	sure the owner and group owner of files located in the /home/jim/*
	directories are above uid=100 and gid=100.  Make sure the user jim
	is created in the unix system password file and his home dir and
	public_html dir exist or this will fail. Make sure mod_frontpage
	is running. If you installed in the order above, mod_frontpage
	may only be loaded when mod_ssl is loaded ('apachectl startssl').
	I'm only touching the brim of problems with frontpage...

	Finding complete documentation on the frontpage owsadm.exe command
	blows.  You will have to experiment or visit microsoft.com and try
	to interpret their ramblings.  I will also gladly try to answer
	any questions if I know the answer.

Nick Rogness <nick at rogness.net> -
  How many people here have telekenetic powers? Raise my hand.
  				-Emo Philips