The implementation (a perl script) is not a one liner, but the execution (calling the perl script) is.
If the OP insists, (s)he could make it a one-liner:
perl -MHTTP::Daemon -E '$d=HTTP::Daemon->new(LocalPort=>$ARGV[0]||8000
+);say$d->url;while(my$c=$d->accept){while(my$r=$c->get_request){$c->s
+end_file_response(".",$r->url->path)}}'
Yes, this is hard to read, hard to remember, and generally a stupid idea.
(And yes, I'm kind of violating my own rule.)
The clean way is to use a script.
Also, writing a module optimized for using in a one-liner isn't that hard:
package HTTP::here;
use strict;
use warnings
use Exporter qw( import );
use Whatever::Webserver::you::like;
our @EXPORT=qw( serve );
sub serve
{
my $port=shift;
$port||=8080;
Whatever::Webserver::you::like->new(port => $port)->run();
}
1;
Using it is as easy:
perl -MHTTP::here -e serve
For a non-default port:
perl -MHTTP::here -e 'serve(8000)'
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|