2 use UNIVERSAL::require;
5 use Maypole::Constants;
14 if ( ( caller(0) )[1] eq "-e" ) {
15 $package->handler() == OK and print $buffer;
22 die "Couldn't require $package - $@" if $@;
24 unshift @{ $package . "::ISA" }, "Maypole::CLI";
27 sub get_template_root { $ENV{MAYPOLE_TEMPLATES} || "." }
30 my ($self,@args) = @_;
31 my ($package, $line) = (caller)[0,2];
32 warn "[$package line $line] ", @args ;
38 my $url = URI->new( shift @ARGV );
40 $self->preprocess_location();
42 (my $uri_base = $self->config->uri_base) =~ s:/$::;
43 my $root = URI->new( $uri_base )->path;
44 $self->{path} = $url->path;
45 $self->{path} =~ s:^$root/?::i if $root;
47 $self->parse_args($url);
51 my ( $self, $url ) = @_;
52 $self->{params} = $url->query_form_hash;
53 $self->{query} = $url->query_form_hash;
56 sub send_output { $buffer = shift->{output} }
61 $package->handler() == OK and return $buffer;
69 Maypole::CLI - Command line interface to Maypole for testing and debugging
73 % setenv MAYPOLE_TEMPLATES /var/www/beerdb/
74 % perl -MMaypole::CLI=BeerDB -e1 http://localhost/beerdb/brewery/frontpage
78 This module is used to test Maypole sites without going through a web
79 server or modifying them to use a CGI frontend. To use it, you should
80 first either be in the template root for your Maypole site or set the
81 environment variable C<MAYPOLE_TEMPLATES> to the right value.
83 Next, you import the C<Maypole::CLI> module specifying your base Maypole
84 subclass. The usual way to do this is with the C<-M> flag:
85 C<perl -MMaypole::CLI=MyApp>. This is equivalent to:
87 use Maypole::CLI qw(MyApp);
89 Now Maypole will automatically call your application's handler with the
90 URL specified as the first command line parameter. This should be the
91 full URL, starting from whatever you have defined as the C<uri_base> in
92 your application's configuration, and may include query parameters.
94 The Maypole HTML output should then end up on standard output.
96 =head1 Support for testing
98 The module can also be used as part of a test script.
100 When used programmatically, rather than from the command line, its
101 behaviour is slightly different.
103 Although the URL is taken from C<@ARGV> as normal, your application's
104 C<handler> method is not called automatically, as it is when used on the
105 command line; you need to call it manually. Additionally, when
106 C<handler> is called, the output is not printed to standard output but
107 stored in C<$Maypole::CLI::buffer>, to allow you to check the contents
110 For instance, a test script could look like this:
112 use Test::More tests => 3;
113 use Maypole::CLI qw(BeerDB);
114 use Maypole::Constants;
115 $ENV{MAYPOLE_TEMPLATES} = "t/templates";
117 # Hack because isa_ok only supports object isa not class isa
118 isa_ok( (bless {},"BeerDB") , "Maypole");
120 like(BeerDB->call_url("http://localhost/beerdb/"), qr/frontpage/, "Got the front page");
122 like(BeerDB->call_url("http://localhost/beerdb/beer/list"), qr/Organic Best/, "Found a beer in the list");
130 for use in scripts. takes an url as argument, and returns the buffer.
135 =head1 Implementation
137 This class overrides a set of methods in the base Maypole class to provide it's
138 functionality. See L<Maypole> for these:
142 =item get_template_root