On Monday 24 July 2006 18:54, Steph Fox wrote:
httpd.conf's weird? It's only a text file :) the complication's in the fact
that there's more than one way to set it up. But you could offer automated
basic CGI setups pretty easily using the paths you've already been given
for php.exe and php.ini, and the module setup actually isn't that
complicated either, assuming you already know it's an apache module setup
that's required.
The problem (and the thing which put me off tackling this on the current
windows installer) is that there are so many ways that a use could have
already set up their httpd.conf (with regard to global and vhost
configurations, whether httpd.conf does all the config, or there are include
files and .htaccess files doing things), the installer would need to more or
less fully understand apache configuration rules to be able to (a) make sure
that php was working at the end of the install, and (b) nothing else was
broken. It would also probably need a massive user interface in order to deal
with the many decisions which would need to be made in order to work out
precisely what to do.
I think you're trying to do too much there. The Apache installer already has an interface for this - and it very simply opens up the httpd.conf for editing!
I was just thinking of the three lines in httpd.conf that are specific to the php.exe or .dll currently being installed - including the one that makes index.php work. If a user already has PHP support in their Apache install they should be able to skip it, but if they don't it'd be good to press a button during PHP install and have Apache 'know' about PHP CGI or module.
Can anyone think of a slick way of dealing with this (and ideally one which
can be implemented from within Wix?
-- Phil Driscoll
-- PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
__________ NOD32 1.1380 (20060125) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com