plack

given the example plack app using lots of middleware components and an mojolicious app enabled in builder (see below), how can i pass parameters from the app.psgi to Mojolicious without using the ugly %ENV hack shown? of cause passing an config is just an example, this could be any scalar/object. app.psgi use Plack::Builder; $ENV{CONFIG} = {...}; builder { ... Mojolicious::Commands->start_app('MyApp'); }; MyApp.pm package MyApp; use Mojo::Base 'Mojolicious'; sub startup { my $self = shift; my $r = $self->routes; $self->config( $ENV{CONFIG} ); $r->route('/')->to('home#'); } This is an

A very popular choice for running Perl web applications these days seems to be behind a nginx webserver proxying requests to either a FastCGI daemon or a PSGI enabled webserver (e.g. Starman). There have been lots of question as to why one would do this in general (e.g. Why use nginx with Catalyst/Plack/Starman? ) and the answers seem to apply in both cases (e.g. allow nginx to serve static content, easy restart of application server, load balancing, etc.) However, I am specifically interested in the pros/cons of using FastCGI vs a reverse-proxy approach. It seems that Starman is widely

Trying handling multiple file uploads with Plack. My form: <form id="file_upload" action="savefile" method="POST" enctype="multipart/form-data"> <input type="file" name="file[]" multiple> <button>upload</button> </form> Selected two files, called: x1 and x2 . The Data::Dumper result of the: my $u = $req->uploads; is $VAR1 = bless( { 'file[]' => bless( { 'headers' => bless( { 'content-disposition' => 'form-data; name="file[]"; filename="x2"', 'content-type' => 'application/octet-stream', '::std_case' => { 'content-disposition' => 'Content-Disposition' } }, 'HTTP::Headers' ), 'filename' => 'x2',

I've been doing web-programming for a while now and am quite familiar with the LAMP stack. I've decided to try playing around with the nginx/starman/dancer stack and I'm a bit confused about how to understand, from a high-level, how all the pieces relate to each other. Setting up the stack doesn't seem as straight forward as setting up the LAMP stack, but that's probably because I don't really understand how the pieces relate. I understand the role nginx is playing - a lightweight webserver/proxy - but I'm confused about how starman relates to pgsi, plack and dancer. I would appreciate a high

Reformulating the question, because @optional asked me it wasn't clear and linked one HTML::Mason based solution Four easy steps to make Mason UTF-8 Unicode clean with Apache, mod_perl, and DBI , what caused confusions the original is 4 years old and meantime (in 2012) the "poet" is created Comment: This question already earned the "popular question badge", so probably i'm not the only hopeless person. :) Unfortunately, demonstrating the full problem stack leads to an very long question and it is very Mason specific. First, the opinions-only part :) I'm using HTML::Mason over ages, and now

I am trying to deploy my little Catalyst web app using Plack/Starman. All the documentation seems to suggest I want to use this in combination with nginx. What are the benefits of this? Why not use Starman straight up on port 80? It doesn't have to be nginx in particular, but you want some kind of frontend server proxying to your application server for a few reasons: So that you can run the Catalyst server on a high port, as an ordinary user, while running the frontend server on port 80. To serve static files (ordinary resources like images, JS, and CSS, as well as any sort of downloads you