Forum

Hi,

This is actually a two-part question.

Part 1:
I'm trying to transition away from apache2 and I run QPSMTPD as a perl cgi in Apache on port 25. The basic Apache example is here: http://wiki.qpsmtpd.org/deploy:apache:apachesmtpdsetup

Can Hiawatha do the same thing using a virtual server config? If so, can you please illustrate what a skeleton config would look like? It looks like I need to hack the Apache::Qpsmtpd module too. That part I can do, but this use might stretch Hiawatha too far.

Part 2:
I've also got a traditional web server on another port that is using PHP/fcgi for doing dev work. This is not set up as a virtual. I just used a the Directory config option to add the path as the first/default web server. Hiawatha is open to the Internet on a non-standard port so I can test remotely. Is this best practices? Or, should I really set it up as another virtual?





Hiawatha version:
Operating System:

1: I don't use both Apache and Perl and have therefor no idea what the Apache configuration shown behind the provided link does. So, sorry. Can't help you with this question.

2: I don't understand your question. Directory or virtual host... as long as it works it's ok, right? There is no such thing as a best practice for that.

I dug into this some more. Essentially, Apache2 is a TCP server with an http module. Mod_perl can work at the TCP level such that it does all the thread management for an application like QPSMTPD.