plack::middleware::file::sass(3pm) [debian man page]

Plack::Middleware::File::Sass(3pm)			User Contributed Perl Documentation			Plack::Middleware::File::Sass(3pm)

NAME

       Plack::Middleware::File::Sass - Sass and SCSS support for all Plack frameworks

SYNOPSIS

	 use Plack::App::File;
	 use Plack::Builder;

	 builder {
	     mount "/stylesheets" => builder {
		 enable "File::Sass";
		 Plack::App::File->new(root => "./stylesheets");
	     };
	 };

	 # Or with Middleware::Static
	 enable "File::Sass", syntax => "scss";
	 enable "Static", path => qr/.css$/, root => "./static";

DESCRIPTION

       Plack::Middleware::File::Sass is a Plack middleware component that works with Plack::App::File or Plack::Middleware::Static to compile Sass
       <http://sass-lang.com/> templates into CSS stylesheet in every request.

       When a request comes in for .css file, this middleware changes the internal path to .sass or .scss, depending on the configuration, in the
       same directory. If the Sass template is found, a new CSS stylesheet is built on memory and served to the browsers.  Otherwise, it falls
       back to the original .css file in the directory.

       This middleware should be very handy for the development. While Sass to CSS rendering is reasonably fast, for the production environment
       you might want to precompile Sass templates to CSS files on disk and serves them with a real web server like nginx or lighttpd.

SASS BACKENDS

       If you have the sass gem version higher than 3 installed and have the "sass" executable available in your PATH, this module automatically
       uses the command to convert Sass or SCSS into CSS. If the command is not available and you have Text::Sass perl module available, it will
       be used. Otherwise you'll get an exception during the initialization of this middleware component.

OPTIONS

       syntax
	   Defines which syntax to use. Valid values are sass and scss. Defaults to sass.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

LICENSE

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Plack::App::File Text::Sass http://sass-lang.com/ <http://sass-lang.com/>

perl v5.12.4							    2011-02-14					Plack::Middleware::File::Sass(3pm)

Plack::Builder(3pm)					User Contributed Perl Documentation				       Plack::Builder(3pm)

NAME

       Plack::Builder - OO and DSL to enable Plack Middlewares

SYNOPSIS

	 # in .psgi
	 use Plack::Builder;

	 my $app = sub { ... };

	 builder {
	     enable "Deflater";
	     enable "Session", store => "File";
	     enable "Debug", panels => [ qw(DBITrace Memory Timer) ];
	     enable "+My::Plack::Middleware";
	     $app;
	 };

	 # use URLMap

	 builder {
	     mount "/foo" => builder {
		 enable "Foo";
		 $app;
	     };

	     mount "/bar" => $app2;
	     mount "http://example.com/" => builder { $app3 };
	 };

	 # using OO interface

	 my $builder = Plack::Builder->new();
	 $builder->add_middleware('Foo', opt => 1);
	 $app = $builder->mount('/app' => $app);
	 $app = $builder->to_app($app);

DESCRIPTION

       Plack::Builder gives you a quick domain specific language (DSL) to wrap your application with Plack::Middleware subclasses. The middleware
       you're trying to use should use Plack::Middleware as a base class to use this DSL, inspired by Rack::Builder.

       Whenever you call "enable" on any middleware, the middleware app is pushed to the stack inside the builder, and then reversed when it
       actually creates a wrapped application handler. "Plack::Middleware::" is added as a prefix by default. So:

	 builder {
	     enable "Foo";
	     enable "Bar", opt => "val";
	     $app;
	 };

       is syntactically equal to:

	 $app = Plack::Middleware::Bar->wrap($app, opt => "val");
	 $app = Plack::Middleware::Foo->wrap($app);

       In other words, you're supposed to "enable" middleware from outer to inner.

INLINE MIDDLEWARE

       Plack::Builder allows you to code middleware inline using a nested code reference.

       If the first argument to "enable" is a code reference, it will be passed an $app and is supposed to return another code reference which is
       PSGI application that consumes $env in runtime. So:

	 builder {
	     enable sub {
		 my $app = shift;
		 sub {
		     my $env = shift;
		     # do preprocessing
		     my $res = $app->($env);
		     # do postprocessing
		     return $res;
		 };
	     };
	     $app;
	 };

       is equal to:

	 my $mw = sub {
	     my $app = shift;
	     sub { my $env = shift; $app->($env) };
	 };

	 $app = $mw->($app);

URLMap support
       Plack::Builder has a native support for Plack::App::URLMap with "mount" method.

	 use Plack::Builder;
	 my $app = builder {
	     mount "/foo" => $app1;
	     mount "/bar" => builder {
		 enable "Foo";
		 $app2;
	     };
	 };

       See Plack::App::URLMap's "map" method to see what they mean. With builder you can't use "map" as a DSL, for the obvious reason :)

       NOTE: Once you use "mount" in your builder code, you have to use "mount" for all the paths, including the root path ("/"). You can't have
       the default app in the last line of "builder" like:

	 my $app = sub {
	     my $env = shift;
	     ...
	 };

	 builder {
	     mount "/foo" => sub { ... };
	     $app; # THIS DOESN'T WORK
	 };

       You'll get warnings saying that your mount configuration will be ignored. Instead you should use "mount "/" => ..." in the last line to set
       the default fallback app.

	 builder {
	     mount "/foo" => sub { ... };
	     mount "/" => $app;
	 }

       Note that the "builder" DSL returns a whole new PSGI application, which means

       o   "builder { ... }" should normally the last statement of a ".psgi" file, because the return value of "builder" is the application that
	   actually is executed.

       o   You can nest your "builder" block, mixed with "mount" (see URLMap support above):

	     builder {
		 mount "/foo" => builder {
		     mount "/bar" => $app;
		 }
	     }

	   will locate the $app under "/foo/bar" since the inner "builder" block puts it under "/bar" and it results a new PSGI application which
	   is located under "/foo" because of the outer "builder" block.

CONDITIONAL MIDDLEWARE SUPPORT

       You can use "enable_if" to conditionally enable middleware based on the runtime environment. See Plack::Middleware::Conditional for
       details.

SEE ALSO

       Plack::Middleware Plack::App::URLMap Plack::Middleware::Conditional

perl v5.14.2							    2012-05-17						       Plack::Builder(3pm)