#Apache app chef install#

To test if content compression works, trace the HTTP request and response before and after enabling this middleware. In our case, there is no option to specify to Plack::Middleware::Deflater, so we use an empty YAML list. The syntax is :Īs key: the name of the Plack middleware to useĪs value: the options to pass it as a list. These lines tell Dancer to add Plack::Middleware::Deflater to the list of middlewares to pass to Plack::Builder, when wrapping the Dancer app.

#Apache app chef install#

First you need to install Plack::Middleware::Deflater, then in the configuration file (usually environments/development.yml), add these lines: plack_middlewares: It's a middleware to encode the response body in gzip or deflate, based on Accept-Encoding HTTP request header.Įnable it as you would enable any Plack middleware. Enabling content compressionĬontent compression (gzip, deflate) can be easily enabled via a Plack middleware (see Plack#Plack::Middleware): Plack::Middleware::Deflater. $ plackup -E deployment -s Starman -workers=10 -p 5001 -a bin/app.plĪs you can see, the scaffolded Perl script for your app can be used as a PSGI startup file.

To start your application, just run plackup (see Plack and specific servers above for all available options): $ plackup bin/app.pl

Unless you have really, really strongly compelling reasons to use Corona, consider using Twiggy or Starman instead. WARNING: Dancer's use of global variables and Coro's threaded behaviors can cause some unexpected behaviors. Twiggy is an AnyEvent web server, it's light and fast. Starman is a high performance web server, with support for preforking, signals and more. Running on Perl webservers with plackupĪ number of Perl web servers supporting PSGI are available on cpan: Starman This option can be useful for small personal web apps or internal apps, but if you want to make your app available to the world, it probably won't suit you. Point your browser at it, and away you go! Simply fire up your app: $ perl bin/app.pl

fcgiĪt the simplest, your Dancer app can run standalone, operating as its own webserver using HTTP::Server::Simple::PSGI. ScriptAlias / /srv/To: AddHandler fastcgi-script. You can use the same technique to deploy with FastCGI, by just changing the lines: AddHandler cgi-script. This option is a no-brainer, easy to setup, low maintenance but serves requests slower than all other options. Now you can access your dancer application URLs as if you were using the embedded web server. ScriptAlias / /srv/ErrorLog /var/log/apache2/CustomLog /var/log/apache2/common

Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Start by adding the following to your apache configuration (nf or sites-available/*site*): The Perl module Plack::Runner is required. cgi files and be able to serve Perl scripts. In providing ultimate flexibility in terms of deployment, your Dancer app can be run as a simple cgi-script out-of-the-box with no additional web server configuration needed. Running as a cgi-script (or fast-cgi) under Apache Running stand-alone behind a proxy / load balancerĭancer::Deployment - common ways to put your Dancer app into use VERSIONĭancer has been designed to be flexible, and this flexibility extends to your choices when deploying your Dancer app.In case you have issues with Template::Toolkit on Dotcloud.Running on Perl webservers with plackup.Running as a cgi-script (or fast-cgi) under Apache.