App-Foca

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    App::Foca::Server - Foca server

DESCRIPTION
    Foca is an application (a HTTP server using HTTP::Daemon) that allows
    the execution of pre-defined commands via, obviously, HTTP.

    Well, lets suppose you have a log parser on all your servers and you are
    in need to parse all of them, the common way would be to ssh to each
    host (can be as simple as ssh'ing to each host or using a multiplex
    tool) and execute your parser, but what if your SSH keys or the keys of
    a user are not there? It will be a heck of pain to enter your password
    hundred of times or lets imagine you want to parse your logs via some
    automation (like doing it from an IRC bot or tied to your monitoring
    solution).. then the problem comes more complex with SSH and private
    keys. With Foca you don't need to worry about those things, the command
    will get executed and the output will be returned as a HTTP response.

    All commands that Foca knows about it are listed in a YAML file. Foca
    uses a default timeout value for all commands but with this YAML file
    you can give a specific timeout to a specific command. All commands are
    executed with IPC (open3).

lib/App/Foca/Server.pm  view on Meta::CPAN


=head1 DESCRIPTION

Foca is an application (a HTTP server using HTTP::Daemon) that allows the
execution of pre-defined commands via, obviously, HTTP.

Well, lets suppose you have a log parser on all your servers and you are in
need to parse all of them, the common way would be to ssh to each host (can
be as simple as ssh'ing to each host or using a multiplex tool) and execute
your parser, but what if your SSH keys or the keys of a user are not there?
It will be a heck of pain to enter your password hundred of times or lets
imagine you want to parse your logs via some automation (like doing it from
an IRC bot or tied to your monitoring solution).. then the problem comes
more complex with SSH and private keys. With Foca you don't need to worry
about those things, the command will get executed and the output will be
returned as a HTTP response.

All commands that Foca knows about it are listed in a YAML file. Foca uses a 
default timeout value for all commands but with this YAML file you can give
a specific timeout to a specific command. All commands are executed with IPC
(open3).



( run in 2.174 seconds using v1.01-cache-2.11-cpan-49f99fa48dc )