However, if you have an C<app.psgi> script, then you no longer
need to specify the PSGI engine. Instead, the L<Catalyst> application class
-now has a new method C<raw_psgi_app> which returns a L<Plack> compatible coderef
+now has a new method C<psgi_app> which returns a L<PSGI> compatible coderef
which you can wrap in middleware of your choice.
Catalyst will use the .psgi for your application if it is located in the C<home>
builder {
enable ... #enable your desired middleware
- MyCatalystApp->raw_psgi_app;
+ MyCatalystApp->psgi_app;
};
And also rename C<< script/myapp.psgi >> to C<< myapp.psgi >>.
+XXX - FIXME - t/psgi_file_testapp_engine_psgi_compat.t
+
If you rename your .psgi file without these modifications, then any tests run via
L<Catalyst::Test> will not be compatible with the new release, and will result in
the development server starting, rather than the expected test running.
=item Catalyst::Engine::Wx
+=item Catalyst::Engine::Zeus
+
+=item Catalyst::Engine::JobQueue::POE
+
+=item Catalyst::Engine::XMPP2
+
+=item Catalyst::Engine::SCGI
+
=back
=head2 Engines with unknown status
The following engines have untested or unknown compatibility. Reports are
highly welcomed:
- Catalyst::Engine::Embeddable - needs testing, should work?
- Catalyst::Engine::XMPP2
- Catalyst::Engine::SCGI
- Catalyst::Engine::Mojo
- Catalyst::Engine::Zeus - broken for ages
- Catalyst::Engine::JobQueue::POE - broken for ages
- Catalyst::Engine::Stomp - fixed
- Catalyst::Engine::Server (Marked as Deprecated)
- Catalyst::Engine::HTTP::POE (Marked as Deprecated)
+=over
+
+=item Catalyst::Engine::Mojo
+
+=item Catalyst::Engine::Server (Marked as Deprecated)
+
+=item Catalyst::Engine::HTTP::POE (Marked as Deprecated)
+
+=back
=head2 Using middleware