William McKee wrote:
On Wed, Jan 14, 2004 at 11:03:12AM -0800, Stas Bekman wrote:

William, you need to move the config files from conf to t/conf and make them test.conf.in and test-ssl.conf.in.


My original goal in putting them in conf was to be able to reuse the
configuration directives for both testing and production. It seems now
that it may be more trouble than it's worth, and that I should stick
with the norm and copy/paste the directives to the t/conf from the
httpd.conf.

Well, I'm sure you can find a way to reuse those. e.g. you could copy the autogenerated .conf files and use them in your production.


usually people put ssl into a separate directory, so you will probably
want to do:

t/conf/extra.conf.in
t/conf/test.conf.in
t/conf/ssl/test.conf.in


I didn't realize that the directives for ssl were usually kept in
separate conf files. Do you add an include in the main conf file to pull
these in?

Not at all, it's just the convention taken by those who added ssl setup to httpd-test and I seem to like this separation. It's good since you have your ssl keys/certs/etc. you don't have to follow that convention.


BTW, A-T has a special module that helps to deal with SSL certs setup (Apache::TestSSLCA). I haven't written it so I won't be much of help, but if you look at httpd-test/perl-framework setup you will see how it's used to automatically generated certificates and ssl setup. If you can write a doc addition about this module and SSL setup in general it'll help a lot too.
But again if what you have works for you, you don't have to use it.


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



Reply via email to