==== NAME ==== Posy::Plugin::BinFile - Posy plugin to serve (binary) non-entry files. ==== VERSION ==== This describes version ``0.62'' of Posy::Plugin::BinFile. ==== DESCRIPTION ==== This plugin renders non-entry files (the 'file' path-type), giving the correct MIME-type for the requested file -- if the file exists in the data directory. This allows you to (a) integrate existing web-pages into a Posy site by putting them into the data_dir(*) (b) include image files alongside entry files by putting them in the same directory (and reference them with relative paths just as you would normally). This depends on the FileStats plugin for the MIME-type information for the files. (*) Note that since Posy recognises and processes '.html' and '.txt' files by default, if you want such files to be processed as raw files and not as Posy-entry files, you need to give them different extensions. This plugin replaces a number of methods, adding in code for dealing with 'file' path-type files. There is no need to add extra actions. == Configuration == This expects configuration settings in the $self->{config} hash, which, in the default Posy setup, can be defined in the main "config" file in the data directory. ``static_file_default_type'' What is the default MIME type for a file when it can't determine the type? (default: "text/plain") ==== INSTALLATION ==== Installation needs will vary depending on the particular setup a person has. == Administrator, Automatic == If you are the administrator of the system, then the dead simple method of installing the modules is to use the CPAN or CPANPLUS system. cpanp -i Posy::Plugin::BinFile This will install this plugin in the usual places where modules get installed when one is using CPAN(PLUS). == Administrator, By Hand == If you are the administrator of the system, but don't wish to use the CPAN(PLUS) method, then this is for you. Take the *.tar.gz file and untar it in a suitable directory. To install this module, run the following commands: perl Build.PL ./Build ./Build test ./Build install Or, if you're on a platform (like DOS or Windows) that doesn't like the "./" notation, you can do this: perl Build.PL perl Build perl Build test perl Build install == User With Shell Access == If you are a user on a system, and don't have root/administrator access, you need to install Posy somewhere other than the default place (since you don't have access to it). However, if you have shell access to the system, then you can install it in your home directory. Say your home directory is "/home/fred", and you want to install the modules into a subdirectory called "perl". Download the *.tar.gz file and untar it in a suitable directory. perl Build.PL --install_base /home/fred/perl ./Build ./Build test ./Build install This will install the files underneath /home/fred/perl. You will then need to make sure that you alter the PERL5LIB variable to find the modules, and the PATH variable to find the scripts (posy_one, posy_static). Therefore you will need to change: your path, to include /home/fred/perl/script (where the script will be) PATH=/home/fred/perl/script:${PATH} the PERL5LIB variable to add /home/fred/perl/lib PERL5LIB=/home/fred/perl/lib:${PERL5LIB} ==== REQUIRES ==== Posy Posy::Core Posy::Plugin::FileStats Test::More ==== AUTHOR ==== Kathryn Andersen (RUBYKAT) perlkat AT katspace dot com http://www.katspace.com ==== COPYRIGHT AND LICENCE ==== Copyright (c) 2004-2005 by Kathryn Andersen This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.