As announced by Sebastian, Mojo::Server::FastCGI is gone from
Mojolicious-1.98 ... thus removing the prime deployment option for
mojolicious in shared hosting environments ... and thus also
removing this option for all the tools built upon Mojolicious.
Today I got the first complaints from a user of remOcular (an
OpenSource tool I published, relying on mojolicious) who suddenly
finds that he can not deploy anymore with the current version.
The Mojolicious changelog sais that the removal was to free the
namespace for a standalone release of Mojo::Server::FastCGI ... is
there an ETA for this ?
As an author, writing software on top of the Mojolicious framework,
such changes are quite unsettling to me as I find parts of my core
environment to be liquid where I had thought them to be solid and
reliable.
I appreciate the idea of having tests for everyting in mojolicious,
but then again, the tests do not make my software work if features
are removed just to increase the test coverage ...
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch to...@oetiker.ch ++41 62 775 9902 / sb: -9900
The Mojolicious changelog sais that the removal was to free the
namespace for a standalone release of Mojo::Server::FastCGI ... is
there an ETA for this ?
As an author, writing software on top of the Mojolicious framework,
such changes are quite unsettling to me as I find parts of my core
environment to be liquid where I had thought them to be solid and
reliable.
I appreciate the idea of having tests for everyting in mojolicious,
but then again, the tests do not make my software work if features
are removed just to increase the test coverage ...