[Catalyst] Maintainability with RequireSSL and the proper way to manage public+secure applicaitons?

Dustin Suchter dsuchter at ucla.edu
Thu Apr 3 03:53:57 BST 2008


So I finally just got RequireSSL installed on my system. I realize 
my current production/development system is not as smoothy 
integrated as it could be. My public site is entirely static HTML, 
while my secure site is a proper Catalyst/MySQL/TT2 application. 
Because of this I chose to have Lighttpd serve static HTML directly 
but pass any requests for the secure site to the FastCGI handler for 
Catalyst. I don't really have a good way to see the static HTML 
content when I'm using the interal Catalyst webserver for development.

So what's the right way to integrate things so that my entire 
system, both development with the Catalyst HTTP::Daemon and the 
production FastCGI system on Lighty, works without significant 
independent configuration and without being horribly un-optimized?

I would actually like to have everything on the same domain and path 
and just use SSL when necessary, hence the interest in RequireSSL.

-d



More information about the Catalyst mailing list