in reply to using HTTP::Daemon instead of Apache
If ease of deployment really matters to you, use HTTP::Daemon. Running a full-fledged Apache for a couple of CGI's and static files may be more resource efficient in the end, but using HTTP::Daemon sounds like it could save a lot of your time over the long term, because you won't have to deal with maintaining Apache.
:)