code like
use Catalyst qw/ ... Static::Simple .../;
That pulls in Catalyst::Plugin::Static::Simple which does the part you're
asking about.
See
http://search.cpan.org/~mstrout/Catalyst-Plugin-Static-Simple-0.29/lib/Catalyst/Plugin/Static/Simple.pm
for
tricks on configuring it to do your bidding.
Also, when running under a webserver such as Apache, you'd likely do some
configuring there to have the webserver send the static files directly
instead of calling on Catalyst to parse through them.
E.g.
http://search.cpan.org/dist/Catalyst-Runtime/lib/Catalyst/Engine/FastCGI.pm#Static_mode
On Wed, Feb 23, 2011 at 7:21 PM, John M. Dlugosz wrote:
static files under /root/images, rather than a controller named Images?
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
On 2/23/2011 6:26 AM, Octavian Rasnita orasnita-at-gmail.com|Catalyst/Allow to home| wrote:
But you can create one or more directory with static files, for example
/images, /js, /css. These directories must be created under the root
directory.
And of course, it is recommended to configure the web server to not send
the requests to those directories to the Catalyst app.
That's exactly what I want. How do I tell Catalyst that /images should beBut you can create one or more directory with static files, for example
/images, /js, /css. These directories must be created under the root
directory.
And of course, it is recommended to configure the web server to not send
the requests to those directories to the Catalyst app.
static files under /root/images, rather than a controller named Images?
And as Carl recommended, it is good to not hard-code the URLS in the
templates because they won't work if you'll want to make some changes and
want to put the whole application to listen to a different base than /, for
example /old-site.
So use $c->uri_for('/path/to/static/file');
or
$c->uri_for_action('/path/to/action'); #for the dynamic pages
I see, so do that for static files too, not just actions?
templates because they won't work if you'll want to make some changes and
want to put the whole application to listen to a different base than /, for
example /old-site.
So use $c->uri_for('/path/to/static/file');
or
$c->uri_for_action('/path/to/action'); #for the dynamic pages
I see, so do that for static files too, not just actions?
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
--
The first step towards getting somewhere is to decide that you are not going
to stay where you are. -- J.P.Morgan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20110223/f1b2a210/attachment.htm
