This is my PSGI script (script/myapp.psgi):
use strict;
use MyApp;
MyApp->setup_engine('PSGI');
my $app = sub { MyApp->run(@_) };
And this is my apache configuration for reverse proxying to Starman:
ProxyPass / http://localhost:3000/
ProxyPassReverse / http://localhost:3000/
<Directory /home/myapp/MyApp/root>
Options FollowSymLinks
AllowOverride None
</Directory>
Alias /css/ /home/myapp/MyApp/root/css/
Alias /img/ /home/myapp/MyApp/root/img/
Alias /js/ /home/myapp/MyApp/root/js/
(I know this could be better :-)
For running the app from the main app directory:
starman -Ilib script/myapp.psgi -p 3000 --workers 3
No problems so far, using the same configuration in 4 applications in
heavy production use.
Regards
J.
El 24/09/11 01:45, Robert Dormer escribió:
Am I to understand that starman is a drop-in replacement for the
fastcgi script, then? I've tried following the instructions from
http://wiki.catalystframework.org/wiki/deployment/perlbal-starman-psgi
with little luck. It seems the provided PSGI script doesn't play well
with Catalyst...
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
